CAPM Practice: Explain the components of an adaptive plan

Rolling wave planning acknowledges that details are only knowable close to execution. Near-term iterations are fully planned; future iterations have only rough outlines. As time passes, the planning wave rolls forward with more detail.

**Why not A:** Planning only three times per year regardless of project pace imposes an arbitrary external cadence that has no basis in agile or rolling wave planning theory. Rolling wave planning is driven by the proximity and detail-readiness of work, not by a fixed annual calendar. Teams using adaptive approaches may plan near-term work in detail every sprint and update medium-term plans at each release boundary.

**Why not B:** Planning only the current iteration with no forward planning ignores the strategic coordination needed to sequence dependencies, manage stakeholder expectations, and prepare upcoming backlog items for refinement. Pure single-iteration planning is a caricature of agile that creates coordination failures in practice. Rolling wave planning maintains forward visibility at a coarser level — not zero visibility — for future work.

**Why not D:** Planning all work in detail from the start and updating monthly describes predictive (waterfall) planning, not rolling wave planning. The fundamental distinction is that rolling wave planning intentionally defers detail until it is knowable and useful — it does not attempt full upfront detail that would be unreliable and expensive to maintain. Monthly updates to a fully detailed plan are also too infrequent for most adaptive project cadences.