The Scrum Guide¶
Schwaber, K., Sutherland, & Jeff. (2020). The Scrum Guide: The Definitive Guide to Scrum. Scrum Guides.
Cited by¶
8 citations across 8 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Operational Period
- Agile software development: the sprint — a fixed-length cycle within which committed scope is closed, with a review and retrospective at the boundary that set the next cycle's scope.
This sourceDefines the Sprint — a fixed-length event of one month or less with committed scope, a Sprint Review, and a Sprint Retrospective at the boundary; new requests are queued for the next Sprint rather than injected mid-Sprint.
Supported in partVerified against the work's full text
The Scrum Guide defines fixed-length Sprints ending with Review and Retrospective, but lets scope be renegotiated mid-Sprint and sets next scope in Sprint Planning.
“They are fixed length events of one month or less to create consistency.”
- Agile software development: the sprint — a fixed-length cycle within which committed scope is closed, with a review and retrospective at the boundary that set the next cycle's scope.
- Rhythm
- The frame sets expectations (everyone knows the demo is Friday), coordinates independent teams by entraining them to a shared beat, and makes deviation legible — a missed cadence event signals trouble in the way a missed beat does.
This sourceDefines the iterative sprint cadence (planning, daily standups, review, retrospective) as a recurring frame that sets shared expectations, entrains independent teams to a common beat, and renders a missed or deviating event immediately legible.
Supported in partVerified against the work's full text
The Scrum Guide supports regular fixed-length events creating consistency and that skipping events loses chances to inspect and adapt, but not entraining independent teams or a missed event signalling trouble.
“Events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.”
- The frame sets expectations (everyone knows the demo is Friday), coordinates independent teams by entraining them to a shared beat, and makes deviation legible — a missed cadence event signals trouble in the way a missed beat does.
Mechanisms¶
- Acceptance Test
- It is the natural fit wherever a contract, a "definition of done,"
This sourceDefines the Definition of Done as a formal quality state that makes completed work transparent.
- It is the natural fit wherever a contract, a "definition of done,"
- Backlog Consolidation
- Regular backlog refinement is the mature planning practice this formalizes.
This sourceIdentifies Product Backlog refinement as the ongoing activity of making backlog items more precise.
- Regular backlog refinement is the mature planning practice this formalizes.
- Commitment Burndown Review
- This is what keeps the ledger alive rather than a stale planning snapshot.
This sourceTreats the Product Backlog as emergent and the Sprint Backlog as a real-time plan updated throughout the Sprint as more is learned.
- This is what keeps the ledger alive rather than a stale planning snapshot.
- Definition of Done
- Its strength is that it gives work a finish line existing independently of the resource container — the core of satisficing, stopping at good-enough rather than optimising without limit — and it makes "done" a shared, checkable fact instead of an individual verdict.
This sourceDefines the Definition of Done as a formal completion state that creates transparency through a shared understanding of completed work.
- Its strength is that it gives work a finish line existing independently of the resource container — the core of satisficing, stopping at good-enough rather than optimising without limit — and it makes "done" a shared, checkable fact instead of an individual verdict.
- Proposition Lifecycle Board
- It cannot slide to Verified on confidence alone; the column's exit criteria — the test passed, a reviewer's sign-off — must be met, and the move records who authorized it, when, and on what evidence.
This sourceDefines completion through explicit exit criteria that an increment must satisfy before it is treated as done.
- It cannot slide to Verified on confidence alone; the column's exit criteria — the test passed, a reviewer's sign-off — must be met, and the move records who authorized it, when, and on what evidence.
- Recirculating Review Loop
- The discipline that guards against both is a fixed definition of done and a hard cycle budget with escalation, so the loop is judged by convergence, not by how thorough the churn looks.
This sourceA Definition of Done supplies a fixed quality state and a target against which progress and completeness can be judged.
- The discipline that guards against both is a fixed definition of done and a hard cycle budget with escalation, so the loop is judged by convergence, not by how thorough the churn looks.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 2 of 8 citations: 2 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 1 other way.
Registry ID ref:db0c55a2a8da · see in the full table