Unclear or Changing Requirements

Warning signs

Rate how often each statement is true of the project today. 0 = Never, 4 = Almost Always.

1. WS1.Stakeholders provide different answers to basic questions about what the solution must do, resulting in inconsistent interpretations of requirements and success.
   0Never1Rarely2Sometimes3Often4Almost Always
2. WS2.Requirements remain vague, high-level, or repeatedly identified as ‘to be defined’ during project execution.
   0Never1Rarely2Sometimes3Often4Almost Always
3. WS3.Requirements change informally or late in the process through unstructured requests, clarifications, or scope adjustments.
   0Never1Rarely2Sometimes3Often4Almost Always
4. WS4.Review cycles reveal surprises, misunderstandings, or differences between stakeholder expectations and what the project is delivering.
   0Never1Rarely2Sometimes3Often4Almost Always
5. WS5.Frequent clarification is required before decisions can proceed because stakeholders and teams do not share a consistent understanding of requirements.
   0Never1Rarely2Sometimes3Often4Almost Always
6. WS6.Teams fill requirements gaps with assumptions, resulting in early rework, inconsistent interpretations, or misalignment across workstreams.
   0Never1Rarely2Sometimes3Often4Almost Always
7. WS7.Stakeholders express growing frustration or confusion about what the project is delivering.
   0Never1Rarely2Sometimes3Often4Almost Always