AgilePM’s control philosophy fixes Time (via timeboxing) and Cost (via stable team size and duration), and protects Quality (it must never be compromised). To keep delivery predictable while remaining responsive to change, contingency is placed in Scope, i.e., Features. Using MoSCoW prioritization, Must Haves are capped, while Shoulds and Coulds provide the controlled flexibility needed to absorb change, manage uncertainty, and still meet deadlines and budgets at the agreed quality level. This approach turns scope into the adjustable “knob,” enabling teams to make informed trade-offs as learning emerges, without eroding the Definition of Done or slipping time/cost constraints. Hence, contingency belongs in Features.