Alright, so the nursery rhyme goes slightly differently. Regardless, I couldn’t resist talking more to the Agile process; since another big dogs has realized the benefit. Adobe (of all folk) has announced the success of using an iterative process in the development of CS3.

Clearly, no one process will rule all. But I still reassert that I like the idea of incremental process.

Do a little…
review…
improve…
repeat…

Most modern processes have such a concept, whether TQM, Six Sigma (DMAIC), BPI, or Lean. I couldn’t imagine going into product development anymore that would last 2 months or more without an iterative based approach. It is too easy to misinterpret, miscalculate, and misunderstand client needs and intentions.

Part of the story also speaks to “Bugalaunch” - the death march to release depriving team members of precious sleep, social lives and undoubtedly personal health. Too often it is the unceremonious end to a project to be rewarded with Bug Hell; which I think exists somewhere around the 222nd layer of the abyss.

This made me realize that it makes the job of motivating developers very difficult, since they never really get a clean, clear reward of a product delivered well and gracefully. I mean, in a traditional Waterfall approach, the chances of something going bad and erasing months of hard work is high. Why not allow for incremental “showing off?” The Agile method allows developers to demonstrate the exceptional work they do gradually. If the project does go awry (for whatever reason), the customer would now be aware of all the good work that happened before a major hurdle is reached. They will therefore be more sympathetic, appreciative and understanding of the hard work it then takes to right the project and overcome the hurdle.

Of course, my developers should beware, because I do like the 20 bug rule too.