Chapter 2. Relying on a Stable Foundation

Software is built to solve complex problems. It is naive to believe that you can write all the requirements from the start and then plan accordingly. Experience teaches you that it does not work this way. It is not realistic to think that requirements are just out there somewhere, and the only thing you need to do is get explanations from stakeholders. More often than not, stakeholders do not know exactly what they want. And if they know what they want, unfortunately they do not agree among themselves. As noted in Chapter 1, “Solving the Right Problem,” when faced with ambiguous requirements, you must stop using traditional management practices and start tackling uncertainties differently.

As strange ...

Get Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery now with the O’Reilly learning platform.

O’Reilly members experience live online training, plus books, videos, and digital content from nearly 200 publishers.