Rolling-Wave Timeline

1  Slide Type Name
Rolling‑Wave Timeline

2  One‑Sentence Purpose Statement
Shows the fully‑detailed near‑term schedule while progressively compressing later periods, so teams can answer “what’s next and how far do we see?” in environments of uncertainty.

3  Visual Description (Designer Instructions)

• Use a 16 × 9 canvas with a single left‑to‑right time axis.
• Wave 1 (Now → +3 months) — occupy ~40 % of the axis width; draw weekly or bi‑weekly ticks and display detailed task bars or milestone dots with labels.
• Wave 2 (+3 → +9 months) — compress scale to monthly ticks; aggregate tasks into higher‑level blocks (e.g., “Feature Set B”); label inside each block.
• Wave 3 (+9 → +24 months) — compress further to quarterly segments; show only phase names or major decision gates.
• Indicate the transition points using subtle vertical “wave dividers” and annotate them (“Detail horizon”, “Planning horizon”).
• Add a bold vertical “Today” marker at the current date.
• Keep colour scheme consistent across waves: one muted fill colour for bars, darker outline for critical items. Use lighter opacity as waves recede to reinforce declining certainty.
• Reserve the bottom 10 % of the slide for a small legend (wave meaning, milestone symbol) and avoid overlap with the axis.

4  Business Questions This Slide Answers

• What exactly must we deliver in the next sprint or month?
• Which larger work‑packages follow, and when do they start?
• How far out is the next major release or decision gate?
• Where does certainty drop off, and where do we need re‑planning?
• Are any near‑term tasks at risk of delaying medium‑term waves?

5  When to Use (Typical Situations)

• Agile program increments that require sprint‑level detail plus release‑train outlook.
• Dynamic environments (R&D, early‑stage startups) where long‑range plans are provisional.
• Steering‑committee updates highlighting what is locked vs. subject to change.
• Rolling‑wave procurement or construction schedules that firm up as designs mature.
• Portfolio roadmaps that mix committed initiatives with tentative future bets.

6  Core Data Fields Required

• Current date (“Today”).
• Detailed task names, start/finish dates for Wave 1.
• Aggregated work‑package names and timing for Waves 2‑3.
• Milestone or gate dates for medium and long term.

7  Optional / Advanced Data Fields

• RAG status or % complete shading on near‑term tasks.
• Confidence level or planning certainty indicator by wave.
• Owner or team label inside each bar.
• Dependency arrows within Wave 1.
• Expected benefit value or capacity load shown under major releases.