Why name sprints by week
Sequential sprint numbers ("Sprint 47") need a lookup table to mean anything, restart awkwardly when
teams merge, and drift apart across teams. ISO week names are self-describing: any person — or script — can
convert 2026-W29 to dates instantly, every team lands on the same name without
coordination, and the names sort chronologically in Jira filters, folder listings, and release notes
forever. The convention scales from one team to a whole engineering org for free.
Picking a cadence: odd/even weeks
For two-week sprints, the standard trick is to start sprints on odd weeks: W01, W03, W05 … Each sprint is then "an odd week plus the following even week", and anyone can tell where in the sprint they are from the week number alone (odd = week 1 of the sprint, even = week 2). Today is week 29, an odd week — sprint start territory.
One-week sprints trivially inherit week names; three-week sprints (W01–W03, W04–W06, …) work but no longer alternate cleanly across years — most teams that choose week-naming settle on one or two weeks.
Naming schemes that sort
| Scheme | Example | Notes |
|---|---|---|
| Full ISO range | 2026-W29-W30 | Unambiguous, sorts perfectly — the safe default |
| Start week only | 2026-W29 | Shorter; fine once cadence is fixed |
| Compact | 26W29 | For branch names and tags |
| Cadence-prefixed | 2W2026.W29-W30 | Encodes the two-week cadence in the name |
Rules of thumb: zero-pad weeks (W07, not W7), keep the four-digit year for anything that outlives a quarter, and use the ISO week-year so late-December sprints don't get the wrong year in their name.
The week-53 and year-boundary cases
Two edge cases decide whether week-named cadences stay clean:
- Week 53. In a 53-week year (next: 2026, 2032, 2037), an odd/even cadence meets a 53rd week and the parity flips — W53 is odd, and next year's W01 is also odd. Pick a policy in advance: run one three-week sprint (W52–W53–W01 spanning the holidays is popular), run a one-week "hardening" sprint for W53, or simply accept the parity flip and restart odd/even in the new year.
- Year boundary. A sprint named
2026-W52-W01is ambiguous about the year of W01. Write both years when a sprint spans them:2026-W52/2027-W01— ugly once a year, unambiguous forever.
Aligning with quarters and release trains
A quarter is 13 weeks — which is not divisible by two-week sprints. Six sprints cover 12 weeks and leave one week over; scaled frameworks turn that into a feature (SAFe's program increments are typically 5 sprints + an innovation/planning week ≈ 11–13 weeks). If your org plans quarterly, the practical pattern is six two-week sprints per quarter plus one flex week — and week numbers make the flex week visible (ISO weeks 1–13 ≈ Q1, 14–26 ≈ Q2, 27–39 ≈ Q3, 40–52 ≈ Q4). Fiscal-calendar organisations should map through real dates instead — see fiscal weeks & 4-4-5 calendars.