Use Cases

Manage Cadences

Set up a program-increment cadence with nested sprints, keep timeboxes rolling, and adjust dates — the admin's recurring job behind every cycle board.

Setting

An agile program runs 12-week program increments (PIs), each made of six 2-week sprints. Several teams plan on the same rhythm. One admin owns the cadences; teams own their folders. Managing cadences needs the Manage org settings capability (default Admin).

Concepts, if they are new: How DevStride manages the When.

Set up the cadences (once)

  1. Open Configure Settings → Cadences and click New Planning Cadence.
  2. Create the parent: Label Program Increment, New Timebox Every 12 Week, Timebox Label Template PI ${counter}, Parent Cadence Root, a Color. Click Create Cadence.
  3. Create the child: Label Sprints, every 2 Week, template Sprint ${ancestor.1.counter}.${timeboxCounter} (→ Sprint 1.1 … 1.6), Parent Cadence Program Increment. Click Create Cadence.

A cadence has no dates yet.

Create the periods

  1. Click New Timebox. Choose Cadence Program Increment. The Label (PI 1), Start date, End date and Length (days) are pre-filled — the first timebox starts today, later ones the day after the previous one ends. Adjust the start if the PI begins on a different day.
  2. Turn on Recursively create child timeboxes. A table shows the six sprints that tile the PI; edit a label or date if needed, or Refresh to recompute.
  3. Click Create.

Every folder whose cadence is Program Increment gets a PI 1 cycle board; every folder on Sprints gets Sprint 1.1 to 1.6. Repeat for the next PI whenever planning needs to see further ahead — many teams keep two PIs of timeboxes open.

Keep it running

NeedDo
The next sprint or PINew Timebox again (or New under Cycle Boards in any folder on that cadence). Dates pre-fill from the last timebox.
Shift dates (a holiday week)Click the timebox bar in the Cadences timeline and edit Start date / End date. Timeboxes on one cadence cannot overlap; gaps are fine; a sprint must stay inside its PI. Cycle boards take the new dates; items on them keep theirs.
Rename a periodEdit the timebox Label. Cycle boards rename themselves.
A new team on the same rhythmNothing here — create the team's folder with Cadence for Cycles set to Sprints. Cycles for every existing timebox appear at once.
A different rhythm (monthly services work)Create another cadence. Teams pick it per folder; a folder's cadence is fixed once it has cycles.
Retire a cadenceRow menu → Archive cadence. Folders and existing cycles stay; no new timeboxes can be added, and the cadence disappears from the folder dialog. Delete cadence is offered only when it has no timeboxes.
Remove a periodEdit the timebox → Delete. Its cycle boards are archived; choose Clear the cycle field on their items or Move to another timebox. A timebox with child timeboxes cannot be deleted until they are.

Why it matters

Because every team's cycles come from the same timeboxes, Track Progress, filters and the Cycle Carry-Forward report line teams up period for period, and nobody types sprint dates into items. The cost is one admin habit: keep timeboxes created ahead of the teams.

Field reference: Cadences. Using the cycles that result: Using cycle boards.