Document Controls
For Application Development & Delivery Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
 |
February 3, 2010 Best Practices: Your Ten-Step Program To Improve Requirements And Deliver Better Softwareby Mary Gerush with Mike Gilpin, Mike Gualtieri, Dave West, Tom Grant, Ph.D., David D'Silva |
Average: 9
(15 ratings)
|
This is an excerpt
Executive Summary
High-quality software requirements sit at the foundation of good software deliverables — those that meet business needs, satisfy customers, and fit into existing technology architectures. Yet many organizations haven't invested much (if at all) in their business analysts' development or requirements practices. If your organization is among these many, it's time to begin a requirements improvement journey. You can't afford not to do it, and a wealth of resources exists: research, educational materials, tools, and communities. Start by educating yourself and your organization on the importance of good software requirements and the cost of poor ones and teaching your business analysts what it takes to define and manage requirements well. Finally, adopt and adapt 10 requirements best practices that we've gleaned from research and discussion with enterprises, vendors, and industry thought leaders. Through improved requirements, you will make better use of scarce resources and satisfy — and perhaps even delight — your organization's employees and customers.
Keywords
TABLE OF CONTENTS
- Mediocre Requirements Cost Organizations Time, Money, And Market Share
- Best Demonstrated Practices In Requirements Definition And Management
RECOMMENDATIONS
- Say "Yes" To Better Software: Start Your Ten-Step Program Today
- Supplemental Material
- Related Research Documents
This is an excerpt
Buy Risk-Free
Price: US $499
Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.
Already a Forrester Client?
Log in to read this document.
