• 1 Status
• 2 Description
• 3 Probability
• 4 Impact
• 5 Response
• 6 Monitoring

PRJR-002: Uncontrolled Scope Creep ¶

1 Status ¶

2 Description ¶

Stakeholders keep adding "small" features directly in review meetings, bypassing the change process. Each addition looks harmless, but together they consume the schedule buffer and blur the release criteria.

3 Probability ¶

4

4 Impact ¶

3

5 Response ¶

Reduce: every new feature request becomes a written change request with an estimate before it is discussed; the release scope is frozen at the iteration boundary and changes are traded, not added.

6 Monitoring ¶

Count the scope changes accepted per iteration; more than two in a row triggers a re-plan of the release date.