Scrum — major processes & flow maps
Diagrams below use ```blueprint-diagram fences on the published handbook; GitHub shows the source as a fenced block. For print/PDF, use the site or export static SVG.
Guide · Updated · Source
1. Sprint lifecycle (high level)
Scrum sprint lifecycle
How refinement, sprint events, and empirical feedback loop through one bounded iteration.
- Sprint lifecycle (high level)Frames one sprint as parallel delivery and inspect-adapt lanes.
- handoffTeams pass refined backlog intent into sprint commitment and execution.
- shared outcomeThe sprint produces a working increment toward the agreed Sprint Goal.
- inspect / adaptScrum events surface progress, quality, and process gaps for adjustment.
- feedbackReview and retrospective outputs feed the next refinement and planning cycle.
Sprint lifecycle (high level)
Lane A ──► handoff ──► shared outcome
Lane B ──► inspect / adapt ──► feedback2. Planning flow (Part 1 → Part 2)
Sprint Planning two parts
How Part 1 sets the Sprint Goal and Part 2 turns selection into a bounded execution plan.
- Planning flow (Part 1Clarifies why this sprint matters and what value it will deliver.
- Part 2)Breaks selected work into a plan the Developers can execute.
Planning flow (Part 1
|
v
Part 2)3. Daily execution loop
Daily Scrum inspect loop
How Developers inspect progress toward the Sprint Goal each day and adapt before continuing.
- Daily execution loopA bounded daily rhythm keeps sprint execution transparent and aligned.
- Current stateThe team reviews work toward the Sprint Goal as it stands now.
- Checkpoint / gateThe Daily Scrum inspects whether the team remains on track.
- refine or escalateOff-track work triggers replanning, scope negotiation, or impediment escalation.
- Continue flowOn-track teams proceed with the agreed sprint plan for the day.
Daily execution loop
Current state
|
v
Checkpoint / gate
|
+-- no ──► refine or escalate
|
yes
v
Continue flow4. Definition of Done gate (increment)
Definition of Done gate
How work earns Done status so the increment stays releasable and transparent.
- Definition of Done gate (increment)Shared criteria govern when backlog items truly complete.
- Current stateWork is assessed against the team's agreed Definition of Done.
- Checkpoint / gateEach item must meet every DoD criterion before labeled Done.
- refine or escalateFailing items are fixed, descoped, or negotiated with the Product Owner.
- Continue flowAccepted work joins the sprint increment as truly Done.
Definition of Done gate (increment)
Current state
|
v
Checkpoint / gate
|
+-- no ──► refine or escalate
|
yes
v
Continue flow5. Stakeholder feedback loop (Review → Backlog)
Review to backlog feedback
How Sprint Review findings return to governed Product Backlog ordering for the next planning cycle.
- Stakeholder feedback loop (ReviewStakeholders inspect the working increment and share grounded feedback.
- Backlog)The Product Owner synthesizes feedback into backlog clarity and ordering.
Stakeholder feedback loop (Review
|
v
Backlog)6. Cross-phase mapping (A–F) in one sprint
| Phase | Where it happens in Scrum |
|---|---|
| A Shape | Continuous refinement + PO/stakeholder work |
| B Plan | Sprint Planning |
| C Build | Sprint execution + Daily Scrum |
| D Verify | DoD, testing in sprint, Review validation |
| E Release | Ship when business chooses (increment is releasable) |
| F Operate & learn | Retrospective; production learnings feed backlog |
7. Flow details (walkthrough)
Sprint lifecycle — Refinement keeps the top of the Product Backlog transparent enough for Sprint Planning to commit. Inside the Sprint, the Daily Scrum inspects progress toward the Sprint Goal; Sprint Review inspects the increment with stakeholders; Sprint Retrospective improves how the team works. Review and Retro outputs feed the next refinement and planning cycle (empirical process: transparency, inspection, adaptation).
Sprint Planning — Part 1 clarifies why this Sprint matters: ordered backlog items; if value or ordering is unclear, return to refinement or a timeboxed spike. Developers select work that fits capacity and agree one Sprint Goal; if confidence is low, remove or swap items. Part 2 breaks work into a plan (often a Sprint Backlog); the Sprint starts when the team agrees how it will meet the goal.
Daily execution — The Daily Scrum is a 15-minute inspect-and-adapt for Developers toward the Sprint Goal; detailed problem-solving happens outside the timebox. Impediments are cleared through the day. The board or backlog should reflect reality by end of day.
Definition of Done — Work is only Done when it meets the shared DoD so the increment stays releasable and transparent. Otherwise fix quality or negotiate scope with the Product Owner—do not label incomplete work as Done.
Review → backlog — The Review grounds discussion in a working increment; the Product Owner synthesizes stakeholder feedback into Product Backlog ordering and clarity for the next Sprint Planning.
8. Authoritative sources & further reading
- The Scrum Guide — Official definition of Scrum (events, accountabilities, artifacts).
- Scrum.org — What is Scrum? — Learning-oriented intro; complements the Guide.
- Agile Alliance — Scrum (glossary) — Short glossary entry alongside the Guide.
- Kanban Guide for Scrum Teams — Blending flow practices with Scrum cadence.
Full curated URL list with executive summaries: External reference URLs (methodology guides).