Document Controls
For Application Development & Delivery Professionals
| Primary Analyst Photo | Document Information | Rate this Document |
|---|---|---|
|
September 28, 2007 Selecting The Right Requirements Management Tool — Or Maybe None Whatsoeverby Carey Schwaber, Peter Sterpe with Mike Gilpin, Catherine Salzinger |
Average: 8
(7 ratings)
|
This is an excerpt
Executive Summary
Many of today's requirements management tool purchases are misguided: Application development and program management professionals often buy requirements management tools for the wrong reasons and select tools that are out of line with their needs. To avoid purchasing tools that are more complex and more expensive than necessary, app dev organizations need to be realistic about the problems that a requirements management tool can address, the level of tooling that they require, and their ability to build and maintain tool integrations.
TABLE OF CONTENTS
- IT Shops Look To Requirements Management Tools For More Than They Should
- Features To Look For In A Requirements Management Solution
- Three Main Types Of Requirements Management Solutions, None Of Them Ideal
RECOMMENDATIONS
- Be Realistic In Your Selection Of Requirements Management Solutions
- Supplemental Material
- Related Research Documents
This is an excerpt
Buy Risk-Free
Price: US $2495
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.
