CAPM Practice: Explain the components of an adaptive plan

Adaptive resource planning operates at multiple levels: a rough capacity plan for the release horizon, refined iteration-by-iteration based on actual velocity and changing priorities. This balances stability with flexibility.

**Why not A:** Adaptive projects absolutely do resource planning — they simply do it at multiple levels of detail rather than in one exhaustive upfront exercise. Claiming no resource planning occurs would make adaptive projects impossible to fund, staff, or schedule at an organizational level. Adaptive planning is rolling and progressive, not absent.

**Why not B:** Hiring resources only after each iteration completes would create severe workforce instability, onboarding delays between iterations, and an inability to maintain the team cohesion that drives predictable velocity. Adaptive teams require a stable core team for Scrum dynamics to function and for velocity to stabilize into a reliable planning signal.

**Why not C:** Locking in resources based on an initial scope estimate is a predictive planning approach that directly contradicts adaptive's fundamental premise of evolving scope. If requirements change substantially across iterations — as they are expected to — a resource plan locked to the original scope becomes progressively misaligned with what the team actually needs to deliver value.