Handbook
Scrum ceremonies → ceremony foundation
**Purpose:** Map **Scrum events** (Scrum Guide) to methodology-neutral **intent types** in [`ceremony-foundation.md`](ceremony-foundation.md).
Scrum ceremonies → ceremony foundation
Purpose: Map Scrum events (Scrum Guide) to methodology-neutral intent types in Ceremony foundation (methodology-neutral).
Canonical Scrum narrative: https://forgesdlc.com/methodology-scrum.html · The Scrum Guide
Events × intent types
Official events are time-boxed; all occur within a Sprint.
| Scrum event | Foundation intents (primary → secondary) | Notes |
|---|---|---|
| Sprint Planning | C2 Commit → C1 Align | Forecast + Sprint Goal + how to deliver; selects Sprint Backlog. |
| Daily Scrum | C3 Sync | Inspect progress toward Sprint Goal; adapt Sprint Backlog; 15-minute time-box for Developers (SM facilitates if needed). |
| Sprint Review | C4 Inspect → C1 Align | Stakeholders on increment; informs future Product Backlog (adaptation). |
| Sprint Retrospective | C5 Improve | Team process, interactions, Definition of Done evolution—not backlog ordering. |
| Sprint (container) | (hosts all above) | Produces Done increment; enables C6 continuously via Definition of Done and integration. |
C6 Assure / release is continuous in Scrum via the Definition of Done and increment quality; formal release (Phase F) may still be a separate org ritual—see project release docs.
What git-based tracking approximates vs what ceremonies need
| Event | Git / commits approximate | You still need (ALM / human) |
|---|---|---|
| Planning | Recent activity, linked work units | Sprint Goal, PO ordering, capacity |
| Daily | Activity per contributor | Verbal/async blockers, coordination |
| Review | Merged work | Stakeholder feedback, acceptance |
| Retro | Throughput themes (weak) | Psychological safety, agreed experiments |
See project TRACKING-CHALLENGES.md.
Suggestions (Scrum-specific)
| Event | Suggestions |
|---|---|
| Sprint Planning | Time-box C1 (why / goal) before C2 (forecast); write Sprint Goal in the tracker. Stop when forecast is realistic, not when every backlog item is discussed. |
| Daily Scrum | Keep C3 only—defer C2 reorder to PO outside the 15 minutes unless team policy allows a short “after the Daily” slot. |
| Sprint Review | Show Done increment only; C4 needs honest feedback, not a status deck. Capture product backlog changes visibly (C1 for next Sprint). |
| Retrospective | C5: one or two experiments with owners; revisit last retro items at the start. |
| Sprint container | Treat C6 as continuous via DoD and integration—don’t skip tests “until the end of the Sprint.” |
For cross-methodology blend tips (e.g. Scrumban), see Methodology bridge — foundation intents ↔ named ceremonies.
Agentic note
Human accountability for commitments and acceptance stays with roles; agents assist execution. Planning and Review still need human intent and DoD ownership—../agentic-sdlc.md.
Canonical source
Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/ceremonies/scrum.md first; regenerate with docs/build-handbook.py.