| Research | Community | Analysts | Teleconferences | Events | Consumer Data | Business Data | Executive Programs | Consulting | About Forrester |
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
![]() |
September 1, 2006 The Root Of The Problem: Poor RequirementsThree Strategies For Addressing Three Types Of Requirements Problemsby Carey Schwaber with Gene Leganza, Megan Daniels |
Average: 9
(6 ratings)
|
This is an excerpt
The quality of software requirements is a limiting factor on the success of software development projects. And it's the rare IT organization that couldn't improve its requirements practices. When it comes to getting requirements right, companies struggle on two primary fronts: requirements definition and requirements management. But the market places a disproportionate emphasis on tools for requirements management. The real opportunity for improvement lies in requirements definition and in how different development methodologies treat changing requirements.
This is an excerpt
Price: US $499
Our Money-Back Guarantee: If you are not completely satisfied, return it for a full refund within three weeks of your online purchase.
Already a Forrester Client?
Log in to read this document.
B2B Sales & Marketing, Corporate Strategy, Application Development, Application Development Management, Application Development Processes & Tools, Application Development Roles & Responsibilities
Footer links (2 lists of links) |