Cadence-Based Planning
Planning sessions held at a predictable rhythm to synchronize teams, set priorities, and commit to the next block of work.
Key Points
- Occurs on a consistent schedule (such as each sprint, iteration, or PI).
- Aligns teams and stakeholders on priorities, scope, and dependencies.
- Time-boxed and data-informed, using capacity, velocity, and feedback.
- Produces a shared, visible plan and an updated backlog for the next cycle.
Example
A product group running two-week sprints holds a planning session every other Monday. Teams review the backlog, discuss cross-team dependencies, confirm capacity, and select the highest-priority work for the next sprint, resulting in a clear plan and commitments.
PMP Example Question
A cross-functional program meets at fixed intervals to review the backlog, resolve dependencies, and agree on what to deliver in the next iteration. What practice is this?
- Cadence-based planning
- Rolling wave planning
- On-demand Kanban replenishment
- Stage-gate governance
Correct Answer: A — Planning at fixed intervals to align teams on work and priorities
Explanation: Cadence-based planning uses a regular schedule to synchronize teams and set priorities for the upcoming timebox, unlike ad hoc or event-driven approaches.