Preface
There is a wide range of books that have been written about specifications. Unfortunately, most of them are not useful for software development teams. These books rely on traditional engineering practices. They assume requirements are known upfront and, once specified, will not change for the duration of the project. And if changes happen, they presume they will be minor, so they could be tracked with a change management process. They promote a sequential process starting with a distinct requirements phase that delivers a detailed requirements specification before starting to design and build the product.
Goal of This Book
It is my belief that traditional engineering practices are not suitable for software development. Central to the ...
Get Executable Specifications with Scrum: A Practical Guide to Agile Requirements Discovery 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.
