⏲️Timeline for Agile Outputs

Here's a recommended progression of when Agile outputs should get created and maintained on Agile teams.

When to Deliver Agile Outputs

Self-organized teams need to make their own decisions about whether and when to deliver Agile-focused outputs. Here are the recommended sequences of delivering these things:

  1. Generating Agile buy-in

  2. Agile team vision

  3. Team RACI

  4. Working agreements

  5. Project phase roadmap

  6. Sprint planning items

  7. Sprint retro

  8. Agile maturity measurements

This visual shows when a team should be working on Agile team outputs. Credit: Tech Fleet.

Before a Project Begins

Team Vision

πŸ‘οΈAgile Team's Visionchevron-right

Working Agreements

πŸ€—Working Agreementschevron-right

Project Roadmap

πŸ“ˆProject Phase Roadmapschevron-right

Roles and responsibility commitments

🦾RACI Chartschevron-right

Backlog and Kanban Board

🍱Backlogs and Kanban Boardschevron-right

Sprint 1 Goals

πŸ§‘β€πŸ’ΌSprint Planning Itemschevron-right

During a Project

New Deliverables

πŸ¦Έβ€β™€οΈSprint Retro Boardschevron-rightπŸ‘©β€πŸ’»Sprint Demo Presentationschevron-rightπŸ“Agile Team Maturity Measurementchevron-right

Maintained outputs

πŸ§‘β€πŸ’ΌSprint Planning Itemschevron-right🍱Backlogs and Kanban Boardschevron-right🦾RACI Chartschevron-rightπŸ“ˆProject Phase Roadmapschevron-rightπŸ€—Working Agreementschevron-rightπŸ‘οΈAgile Team's Visionchevron-right

Last updated