BC1-90 Day Rolling Backlog

  2. /
  3. Basecamp 1
  4. /
  5. BC1-90 Day Rolling Backlog

Why

​​​​​​Rolling backlogs provide just enough horizon for the consuming team to perform well at a predictable level without wasting too much time planning up front or too much time reacting at the last minute. We will establish an end-to-end cadence of progressive elaboration of Epics and Features to Stories and make planning a sustainable process that is embedded in the teams.

How

Teams have understanding of priorities and are able to use the Epic Roadmap to have a continuously current view at least 6 months out. Product Line Teams are able to use this horizon to know what is coming up for the next release and are able to refine the Features to meet expectations. Delivery Teams are able to work deeper into their backlog and refine work further in advance.

Delivery Teams should have time to do research spikes in order to help Product Line Teams come up with the best solution.

Teams will be using the knowledge of the Roadmap, Strategic Alignment and refined work to write better Features and User Stories. This process is now becoming more of an art than a science; teams are fully functioning and know what they need from each other.

Success Criteria

  • Roadmap items (Epics and Features) are vetted and elaborated iteratively and incrementally within the established Product Line Team cadence
  • The cadence is sufficient enough to maintain 3+ sprints of ready backlog consistently (measured at the time of sprint planning)
  • 3 months of rolling Feature backlogs to refine for Product Line Teams
  • Backlog depth is sufficient to manage business expectations/predictability

Supporting Material 

Coaching Activities

 

Maintain Rolling Backlog

Basecamp 1 Outcomes

Form Teams     |     Establish Flow of Work     |     Make & Meet Commitments   |     Improve the system     |     Stable Throughput     |     Road Map     |     Release Plan     |     90 Day Rolling Backlog