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 o...
- Chapter 18. Requirements Analysis Toolkit
- from Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise
- Publisher: Addison-Wesley Professional
- Released: December 2010
User stories and natural language are not always sufficient to communicate the full complexity of requirements. In these cases, you may need to apply more technical methods. This reading discusses several specification techniques that can help reduce the confusion that often exists in defining complex requirements.
Share this highlighthttp://www.safaribooksonline.com/a/agile-software-requirements/99229/