The pitfalls of traditional big upfront requirements

In Chapter 1, The Software Industry and the Agile Manifesto, we took a look at some of the issues that the software industry faced prior to the Manifesto for Agile Software Development and the formation of the Agile Alliance in 2001.

The main issues we saw were related to attempts to control projects through predictive planning, an approach which requires gathering all requirements up front so that a detailed estimate can be made to determine project costs and timelines.

Business Analysts (BAs) often write traditional requirements documents and carry out the analysis work as well, either simultaneously or as a subsequent phase.

A traditional requirements document might contain the following: ...

Get The Agile Developer's Handbook now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.