
Guest Post by John Ayers (first posted on CERM ® RISK INSIGHTS – reposted here with permission)
Some common reasons why requirements can cause risk to a project are:
- To be determined (TBD)
- Late requirements definition
- Unclear requirement definition
- Changing requirements
- Late requirement flow down to subcontractors
- Incorrect or poorly defined interface documents
This paper explains how poorly defined requirements can impact the project.