The Elements of Scrum summary

Tradition may have its charm, but it has few fans when it comes to technology development. Technology needs to be constantly updated to remain relevant; in fact, being current is essential not only to technology but also to the processes used to create it.

One system of development is called the waterfall method, which is a finish-to-start process for producing software. In such a system, a software team would typically compile requirements, make a design, write code, test and then deliver a finished product.

The “finish-to-start” aspect of the process is crucial. Activity A must be completed before work on activity B can start. For instance, you can’t begin testing a design until you’ve finished coding.

Why do people and organizations like this method?

By separating each development step, scheduling and planning is made easier. Managers often prefer a waterfall approach as they believe it allows them greater accuracy in scheduling and allocating budgets.

But the waterfall method isn’t very reliable. Software is often too complicated a product to be fully designed before production starts. Therefore, if you demand a perfectly designed product, you’ll be left with little wiggle room for change during production.

So while it’s possible for a perfect design to seamlessly transition to a perfect production process, this usually only occurs when you’re producing a static object, like a car. In this example, you’d design every element in the car, then follow those design directions to the letter during manufacturing.

But software production, in contrast, is just too complex.

So, while designers may come up with what they think is a perfect product, complications are sure to arise when designs are applied. The numbers tell the tale: only 16 percent of waterfall-method projects meet completion deadlines, while 31 percent are cancelled and 53 percent go over budget!

How do you avoid such a pitfall in your own projects? Read on to learn more.