Thinking Lean: How Much Requirements Documentation Is "Just Enough"?
Forrester's AD&D Community Offers Relevant Insight And Pragmatic Advice
December 29, 2010
Why Read This Report
In traditional app dev shops, business analysts (BAs) create standardized, lengthy, text-heavy Microsoft Word documents to represent software requirements, but creating and consuming this documentation takes time that most BAs and stakeholders just don't have. On the other hand, Agile methods advocate that teams create "just enough" requirements documentation to meet the need. They use less-formal documentation, more pictures, and less text. Traditional shops have heard the "just enough" message, but they don't know how to apply it in their environments. The Forrester Community For Application Development & Delivery (AD&D) Professionals offers advice: By considering the documentation's intent and consumers, team dynamics, and the project/problem at hand, business analysts and other requirements authors can determine how much requirements documentation is "just enough" to maximize value and eliminate waste.
Already a Client?
Log in to read this document.
Become a Forrester Client
Customers are the new market-makers, reshaping industries and changing how businesses compete and win. Success depends on how well and how fast you respond. Forrester Research gives you insights and frameworks aligned to your role to shorten the time between a great idea and a great outcome, helping your teams win in the age of the customer. Contact us to learn more.
This report is available for individual purchase ($499 USD).Purchase
Right Tools. Write Requirements. Right On!
June 24, 2010 | Mary Gerush
Brief: Software Requirements Practices Are Ripe For Disruption
April 25, 2014 | Kurt Bittner
It's Time To Move Your Business Analysts To An Adaptive, Tool-Kit-Driven Requirements Approach
February 10, 2011 | Mary Gerush