Release-Train / Increment Timeline

1  Slide Type Name
Release‑Train / Increment Timeline

2  One‑Sentence Purpose Statement
Answers “what will ship in each fixed cadence (sprint, program increment, or release train) and when.”

3  Visual Description (Designer Instructions)

• Create a 16 × 9 slide with a horizontal band representing the overall planning window (e.g., 12 months).
• Segment the band into equal blocks for each cadence unit: Sprints (2 weeks), PIs (10–12 weeks), or Releases (quarterly). Place a thin vertical line at every cadence boundary; label each block at the top (“Sprint 10”, “PI 3”, “R2026‑Q2”).
• Directly beneath each block header, add a neatly stacked list (or small pill‑shaped tags) of the features / user stories / epics committed to that increment. Use a consistent muted colour fill for each feature tag; keep text to one line.
• Draw a lightweight horizontal baseline under the feature tags and place milestone diamonds below the cadence boundaries if a gate (e.g., “Hardening Sprint”, “Release Freeze”) exists. Connect successive milestones with a subtle line to emphasise the continuous train.
• Highlight the current increment block with a soft shaded background and add a vertical “Today” marker passing through it.
• If showing multiple trains (e.g., Front‑End, Back‑End), stack additional rows of cadence blocks underneath, perfectly aligned so boundaries line up vertically.
• Reserve the top 15 % for a headline and a concise legend (colour meaning, feature tag style); keep legend elements clear of the timeline. Use a sans‑serif font—block labels 11 pt bold; feature tags 9 pt regular.

4  Business Questions This Slide Answers

• What functionality is planned for each upcoming increment?
• Which increment are we in right now, and what’s next?
• How far out are critical gates such as release freeze or hardening?
• Are multiple trains synchronised on the same cadence boundaries?
• Where do backlog items still need grooming (empty or light blocks)?

5  When to Use (Typical Situations)

• SAFe program‑increment planning or big‑room planning outputs.
• Scrum‑of‑Scrums reviews aligning multiple squads’ sprint objectives.
• Release‑train engineer updates to executives.
• Product‑roadmap presentations to sales or customers that rely on cadence.
• Post‑mortems comparing planned versus delivered scope across increments.

6  Core Data Fields Required

• Cadence unit names and exact date ranges.
• Feature / epic titles assigned to each unit.
• Current date for “Today” marker.
• Optional milestone labels (release freeze, hardening, GA).

7  Optional / Advanced Data Fields

• Feature size or story‑point estimate shown as tag width or badge.
• RAG or confidence indicator per feature or increment.
• Owner squad initials on each feature tag.
• Dependency flags or icons if a feature relies on another increment.
• Cumulative velocity trend displayed as a small line graph above the band.