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
Learn how IT can better guide its strategic investments and operational resource allocation throughout the service lifecycle. With Service Portfolio Management, IT investments and resources are translated into things the business cares about – services. Download the white paper Service Portfolio Management: Manage IT For Business Value.
Don't re-invent the wheel! Why divert resources to developing business intelligence and analytics functionality when partnering results in improved productivity and more innovation? Check out this IDC white paper from SAP to see why partnering with an established BI vendor presents a compelling economic case.
Register Today and Save 15%!
Register now for a webinar on March 23rd: Looking for a Project and Portfolio Mgmt software?
|
| ||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||