Project Smart ~ Exploring trends and developments in project management today

Calendar icon
Adobe PDF icon

Waterfall Software Development: The Illusion of Risk Management

~ By Rodney J Smith

Agile and waterfall tag cloud

High profile IT project failures are nothing new; in fact few projects are 100 percent successful in delivering everything the customer wants on time and within budget. So it is small wonder that businesses put loads of effort into trying to minimise the risk of their projects becoming one of these statistics.

The traditional way of doing this is to spend considerable time and effort gathering together all the requirements for a new system, then designing a complete solution up front, from which detailed programming estimates can be produced. The theory behind this so-called Waterfall methodology is that the estimates (and thus budget) will be accurate, and there will be no major surprises once development gets underway. Unfortunately this approach is based on a number of faulty assumptions, which means it rarely works in practice!

Assumption: It's Possible to Identify a Complete Set of Requirements Up Front

In fact, building a computer system is akin to driving down a country lane at night; the driver can only ever see as far as her headlights allow, but each bit of progress that is made illuminates areas that could not be seen at the start. This is true even in domains that are relatively well understood.

Assumption: The Requirements, Once Identified, Will Not Change

There is an inevitable lag between initiation of a software project and its eventual delivery, and even if it were possible to identify a complete and accurate set of requirements up front (it's not - see above), the constantly changing business landscape dictates that requirements will change along the way. Waterfall projects typically resist absorbing such changes due to the knock-on effect on the design and schedule, with the result that the eventual delivered system does not match the (current) requirements.

Assumption: It's Possible to Produce Estimates With a High Degree of Accuracy

Surprisingly, a number of studies indicate that on average, fixed scope projects cost almost twice as much as estimated. Apart from the problems of changing requirements, this may be in part due to initial estimates being artificially low in order to secure contracts in the first place.

Assumption: The Development Phase Is Simply a Mechanical Process of Transforming the Design Into Code

This is where software development suffers because of attempts to liken it to the (building) construction industry. In fact, there is a lot of art in the craft of programming, which makes it a lot less predictable than managers would like.

As much as corporate managers would dearly love the Waterfall approach to work, in practice it is extremely unreliable, inefficient and inflexible. Yet in spite of credible alternatives (the Agile family of methods) which appear to deliver far better results in practice, managers frequently persist with this discredited methodology because of the illusion it projects of being less risky and allowing them to remain in control.


Comments

Be the first to comment on this article.

Add a comment



(never displayed)



 
2000
Enter the last letter of the word satellite.
Notify me of new comments via email.
Remember my form inputs on this computer.

My Story: Working Smarter; Not Harder

Woman thinking with a light bulb drawn on a blackboard

When you realise that you have the power to change your beliefs and remove a limiting factor that has been constraining you, you have an AHA! moment.

The Mythical 50% Resource

Red blocks with the percent sign on a white background

Most managers of software development projects have had an encounter with a resource who is committed to their project some percentage of the time.

How to Avoid Project Burnout

Exhausted businessman resting on a pile of paperwork with tongue hanging out from overwork

Resources on projects can be susceptible to burning out before the project finishes. Here are a few ideas to prevent burnout in project teams.

Which Life Cycle Is Best for Your Project?

Life cycle written on digital touch screen

When choosing a development life cycle, don't just trust your feelings. Decide based on factors that really matter.

PROJECT SMART is the project management resource that helps managers at all levels improve their performance. We provide an important knowledge base for those involved in managing projects of all kinds. With weekly exclusive updates, we keep you in touch with the latest project management thinking.

WE ARE CONNECTED ~ Follow us on social media to get regular updates and opinion on what's happening in the world of project management.


Latest Comments

Jacob Gubler commented on…
Better Coaching Using the GROW Model
- Thu 24 October 4:50pm

malyn manceras commented on…
Better Coaching Using the GROW Model
- Fri 18 October 5:25am

Martha Hayes commented on…
Better Coaching Using the GROW Model
- Thu 17 October 6:50pm

Latest tweets

General Project Management • Re: Automatic resource allocation depending on tasks - help! https://t.co/GyLi8qPMob about 2 days ago

General Project Management • Project Management Documentation: RAID!! https://t.co/Ww0u4rdQdj about 9 days ago

General Project Management • Re: Automatic resource allocation depending on tasks - help! https://t.co/Y80spWTlz4 about 10 days ago