SDLC blueprint

Handbook

Scrum — major processes & flow maps

Mermaid diagrams below render on GitHub and in many Markdown viewers. For print/PDF, export from Mermaid Live or duplicate in draw.io.

Scrum — major processes & flow maps

Mermaid diagrams below render on GitHub and in many Markdown viewers. For print/PDF, export from Mermaid Live or duplicate in draw.io.

1. Sprint lifecycle (high level)

flowchart LR subgraph refine[Ongoing refinement] R[Refinement] end subgraph sprint[Sprint] P[Sprint Planning] D[Daily Scrum loop] V[Sprint Review] RT[Sprint Retrospective] end R --> P P --> D D --> D D --> V V --> RT RT --> R

2. Planning flow (Part 1 → Part 2)

flowchart TD A[Product Backlog top items] --> B{Value clear & ordered?} B -->|No| C[Refinement / spike] C --> A B -->|Yes| D[Select PBIs for capacity] D --> E[Draft Sprint Goal] E --> F{Team confident?} F -->|No| G[Remove or swap items] G --> D F -->|Yes| H[Part 2: break into Sprint Backlog] H --> I[Sprint starts]

3. Daily execution loop

flowchart TD S[Start of day] --> M[Daily Scrum 15m] M --> W[Work toward Sprint Goal] W --> I{Impediment?} I -->|Yes| X[SM / team remove blocker] X --> W I -->|No| W W --> E[End of day: board updated] E --> S

4. Definition of Done gate (increment)

flowchart TD C[Code complete] --> T[Tests pass / agreed quality] T --> R[Review / PR merged per policy] R --> Doc[Docs & release notes if required] Doc --> Rel{Release-ready per DoD?} Rel -->|Yes| Done[Done increment] Rel -->|No| Fix[Fix or pull from sprint scope] Fix --> C

5. Stakeholder feedback loop (Review → Backlog)

flowchart LR Demo[Increment demo] --> FB[Feedback captured] FB --> PO[PO synthesizes] PO --> BL[Product Backlog updates] BL --> NS[Next Sprint Planning input]

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

Full curated URL list with executive summaries: REFERENCE-LINKS.md.

Canonical source

Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/scrum/process-and-flows.md first; regenerate with docs/build-handbook.py.