Workflow Analysis
Intake to deployment & handoff delays
Scrum Master Guide: Workflow Analysis
Workflow Analysis traces work from intake to deployment, uncovering bottlenecks, handoffs, and delays that sprint-level metrics miss. Each transition between stages has two components: active work time and handoff delay (idle time waiting for the next stage to pick up). High handoff delays often point to capacity gaps, unclear ownership, or missing automation.
Workflow Stage Flow
Active time (blue) + handoff delay (amber) per transition
Transition Breakdown
Idle % > 30% highlighted in red
| Transition | Active Time | Handoff Delay | Total | % Idle |
|---|---|---|---|---|
| Intake → Triage | 4h | 2h | 6h | ⚠ 33% |
| Triage → Development | 8h | 12h | 20h | ⚠ 60% |
| Development → Review | 24h | 6h | 30h | 20% |
| Review → QA | 8h | 16h | 24h | ⚠ 67% |
| QA → Deploy | 4h | 8h | 12h | ⚠ 67% |
API Explorer
Reducing Handoff Friction
Retrospective
Present the handoff delay data. Ask: 'Where does work sit waiting?' The Review→QA transition often has the highest idle time — is it a reviewer capacity issue or an unclear QA handoff process?
Planning
Set WIP limits per stage based on where idle time concentrates. If Development→Review has a 6-hour delay, the team may need to prioritize reviews before starting new work.
Process improvement
Target the single worst handoff each quarter. Reducing one transition's idle time by 50% has more impact than small improvements across all stages.