HKSM
Cadence
A steady, repeatable pace that organizes how a team plans, executes, and reviews work, typically using fixed-length timeboxes (such as sprints).
Key Points
- Defines a predictable tempo for events, work cycles, and delivery checkpoints.
- Often implemented through timeboxes like 1- to 4-week iterations (see also Timebox).
- Supports forecasting and flow by reducing variability and context switching.
- Should be sustainable and adjusted empirically based on team capacity and outcomes.
Example
An agile product team adopts a 2-week sprint cadence with a daily stand-up at 9:00 a.m., backlog refinement every Wednesday, a sprint review and retrospective on the last day of each sprint, and a release at the end of every second sprint.
PMP Example Question
A team decides to run 2-week sprints, hold daily stand-ups at the same time each day, and release on the last business day of each month. What are they primarily establishing?
- Cadence
- Critical path
- Timebox
- Velocity
Correct Answer: A — Cadence
Explanation: They are defining a recurring rhythm for planning, execution, and delivery. A timebox is a fixed-length container for work (e.g., the 2-week sprint), while cadence is the overall steady tempo across events.
