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
Type the numbers for two hundred thirty-one.
Notify me of new comments via email.
Remember my form inputs on this computer.

10 Principles of Good Project Management

A project management workflow diagram written on yellow sticky notes

This article details ten solid principles of project management that are crucial to achieving your goals.

Taming MS Project

Gantt chart and plan

Microsoft Project can become a huge overhead, even for seasoned project managers. This article contains some tips and tricks that will help you tame the tool.

How to Become a Project Manager

Senior lecturer in front of his class

If you're new to project management don't be bamboozled by all the jargon. This article sets out the skills needed to become a competent project manager.

Learning from Project Failures

Success and failure directional signs

Some of the most important lessons we learn come from failures. Kenneth Darter explains a simple four step process to make sure the same failures aren't repeated.

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

Peter Earnshaw commented on…
Pareto Analysis Step by Step
- Tue 4 February 2:03am

Lesiba Matlou commented on…
Writing a Funding Proposal
- Sun 26 January 5:18am

Tim Rumbaugh commented on…
10 Golden Rules of Project Risk Management
- Sat 28 December 6:48pm

Latest tweets

General Project Management • Re: PMP formulas cheat sheet https://t.co/lC4ZSfYPsx about 23 days ago

General Project Management • PMP formulas cheat sheet https://t.co/b4C2fpdWqN about 25 days ago

General Project Management • Implement a new audio and video recording system? https://t.co/SY5tnWhZTu about 29 days ago