Skip to main content

XP is to Development Process what GOF is to Software Design

The problem I see with most objections to Extreme Programing (XP) and Agile development is that they are often speculations on theory, rather than wisdom based on actual practice. It's amazing to see the amount of time and energy people spend in *discussing* process than actually building something and learning from the experience.

The following is my real-world take on this subject, directed at no one in particular, but at everyone in general who is critical or afraid of XP (often the same people who don't have meaningful experience of using it):

XP is a process that has *evolved* through the collective experience of programmers through the mess that the software industry had become- always late, always over-budget, always buggy. And we were told to accept it as a fact of life.

In the midst of all the chaos, there were programmers working after hours doing what they weren't allowed to do during the day - writing tests for code (TDD), automating builds and tests (continuous build & integration), fixing things they were not supposed to fix (refactoring), working with their like-minded colleagues (pair-programming) on weekends to ensure they got a lot done without the "inevitable bugs" which would have brought down the fury of the management upon them, ... and so on.

XP and Agile brought us all out of the closets.

That's why only experienced people with open-minds find it easiest to adopt XP. Or fresh out of college students or young programmers who have not yet been corrupted by the "you're too good to write tests- you'll only do coding" crap they often get fed.

To me, questioning XP without learning XP is like questioning the Gang-of-four Design Patterns before you have any serious programming background solving the problems solved by the GOF patterns.

Design patterns *evolved* after years of people doing things the wrong way, before they learned the right way. Design patterns teach us how to write good code by learning from the mistakes made by smart, experienced programmers before us and the lessons they learned.

*** Design Pattens are Best-practices for programming, solving most typical programming problems.

*** XP/Agile are Best-practices for product/project development process, solving most of the typical process problems:
  • requirements gathering, 
  • estimating and scheduling work, 
  • measuring progress, 
  • managing change, 
  • getting feedback early & often, 
  • continuous knowledge transfer & peer-review, 

... the list is long.

Comments

Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint:

Manage Unfinished Work - Split user stories (new link)

Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):
This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying acceptance criteria, in response to t…

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is.

Allow me to explain.

The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with.

Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria.

Describing all the requirements as User Stories for a decent sized product is rigoro…

To dream or not to dream? How about keeping your mouth shut?

Here's a really nice quote from one of my dear friends in response to one of my dreams.
Between the bigger things you cannot do,and the smaller things you don't want to do,you may end up doing nothing The problem with quotes and analogies is that they are almost always approximately appropriate, but rarely if ever exactly applicable . A quote is by definition a generalization. Also, we are by nature biased with our prejudices, biased by our own very personal and unique experiences, and biased, by nature, against those who are near and dear to us. While we want them to succeed and would eventually be happy if they succeed big, our natural instinct is to "help" them "stay grounded".

I disagree with this helping nature, of course. I can - and will- expound on the virtue of dreaming big and having a big mouth. But that will be another day.

Today I'm going to present a few quotes on the flip-side of my friend's quote. Feel free to add yours to the list…