Requirement Management Failures and Fixes |
||||||||||||||||||||||||||||||
|
|
Home > Articles >
The Chaos Report is a frequently referenced study that provides statistics on IT implementation failures and successes. You likely don’t need another industry statistic to understand poorly defined requirements result in poor project outcomes. While developing a lecture on requirements management, I found a few examples of project failure. The following categories are not a definitive list, but represent a high-level categorization of sources for requirement management failures.
Poorly Defined Requirements
We’ve all heard the phrase “Garbage in, garbage out.” A few years ago, a system implementation project suffered from poorly defined requirements and resulted in a failed project. The business customers thought they were providing good requirements for system development but ended up with garbage and fodder for this story.
The original scope of the project was to develop a simulation tool for a Microsoft Access database application.
Please login/register to read the entire article.
sponsored announcements and special offers
Difficult for competitors to equal. EMA reviews IBM Rational's new quality & requirements management offerings. The verdict, "For companies seeking to improve ROI delivered by software projects,we believe Rational's value proposition is difficult to match."
Microsoft Project Conference 2000
Use WorkLenz PPM to Manage Agile Software Development
|
| ||||||||||||||||||||||||||||