The number 1 reason projects fail. 

Requirements - Unclear, lack of agreement, lack of priority, contradictory, ambiguous, imprecise.

Per research conducted by Michael Krigsman for Beyond It Failure published March 15, 2011.

PD Mentors offers three Requirement Management related courses for as low as $125 per student per day. All courses include reinforcing exercises and can be delivered in a workshop format; using your project as the exercise material.

Requirement Development

Concepts Architecture and Design

Integration Verification and Validation

Extracted from Requirements Development Best Practices Document

Success Factors

Requirements Development is a methodical process to ensure availability of correct decision criteria for selecting solutions (concepts and architectures) for the product or system of interest.  To ensure proper requirements development:

• Install a systematic requirements development process
• Implement Requirements Review decision gates
• Require User Concept of Operations artifacts for each decision gate
• Require a weighted solution selection criteria.

Warning Signs

Early warning signs for a flawed requirements development process are:

• Stakeholders not solicited
• All Stakeholders not considered
• User CONOPS not developed
• Requirements not weighted
• Requirements not prioritized
• Solution selection criteria not defined

See PD Mentors Requirements Development course outline here.