Chapter 18. Requirements Analysis Toolkit
There is no sense in being precise about something, when you don’t even know what you are talking about.
—John Von Neumann
Smaller projects, such as those that can operate solely at the Team level, are usually so well contained that communication among the stakeholders is not a big issue. The team usually has easy access to each other, and it’s easy to resolve ambiguities and confusion. Just lean over to the next workstation, and ask the product owner what they meant with a story!
However, as projects grow in scope and size, the communication pathways become more and more complex, and opportunities for misunderstandings arise. Indeed, as projects grow to the Program level, it’s pretty much a given ...
Get Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise 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.
