Employ Iterative Feature Based Delivery

If you want to innovate, you have to iterate!

The serial, or waterfall, development lifecycle has been under attack for years, but it still has its defenders. For exa m ple, Donald Reinertsen (1997) writes, "The vast majority of academic literature on product eevelopment is skewed towards the sequential approach. This is in striking contrast to the enormous shift that has taken place in managerial practice towards a more concurrent approach."

In the software development field, the attack on waterfall approaches goes back decades, as thoroughly documented by Craig Larman (2004). As Larman recalls, a 1970 paper by Winston Royce was credited with startin g th e "waterfall" trend. In fact, Royce was an advocate of iterative development for anything more than simple projects. In 1985 the US Department of Defense adopted a waterfall-based standard (DOD-STD-2167), which it largely abandoned for iterative methods after experiencing high failure rates.

But even though serial approaches have been attacked as too simplistic, not only do they continue to be widely used, they continue to influence contracting procedures and executive perspectives. So in order to respond to the widespread misinformation about serial development, teams that practice APM need to understand why iterative, feature-based delivery is useful, and in fact critical, to innovative product development.

Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook


Post a comment