2018 Kanban Guide for Scrum Teams

occur "just in time" or on a cadence. Any circumstance influenced by the five activities within a Sprint might trigger a flow-based retrospective.

flow-based retrospectives need not coincide within the boundaries of a Sprint. They can

flow-based Sprint Retrospective adds the inspection of flow metrics and analytics to help determine what improvements the Scrum Team can make to its processes, including the Sprint
Retrospective itself. The Scrum Team using Kanban also inspects and adapts the policies in its
Kanban system to optimize the flow in the next Sprint.

Flow-Based Sprint Retrospectives

about monitoring progress towards a goal.

The Scrum Guide provides a detailed outline of the Sprint Review process. In addition to these activities, inspecting Kanban flow metrics as part of the Sprint Review creates opportunities for new conversations

Flow-Based Sprint Review

What work items are blocked and what can the Scrum Team do to get them unblocked?
•
What is the age of each item in progress? What work items have violated or are about to
• violate their SLE and what can the Scrum Team do to get that work completed?
Are there any things that may impact the Scrum Team's ability to complete work today
• that is not represented on the board?

additional things to consider during a flow-based Daily Scrum are as follows:

Flow-Based Daily Scrums
A flow-based Daily Scrum focuses on ensuring the Scrum Team is doing everything it can to maintain flow every day. While the goal of the Daily Scrum remains the same as in The Scrum
Guide, the meeting itself takes place around the Kanban board and focuses on where flow is lacking and on what actions the Scrum Team can take to get work flowing again.