Purpose
When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.
Agile Framework
Scrum
Manages complex product work empirically through transparency, inspection, and adaptation in Sprints.
Scrum defines the Scrum Team, five events, three artefacts, and their commitments. Product Goal, Sprint Goal, and Definition of Done create focus and transparency; the framework does not prescribe Kanban WIP limits.
How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?
- Participants
- 3-10 (Scrum Team)
- Time
- 1-4 Wochen je Sprint, laufend
Scrum uses Sprints with Planning, Daily Scrum, Review, and Retrospective around three artefacts and commitments. Assessments remain justified and context-bound.
Product Goal
Product Goal
Make Product Goal and ordered Product Backlog transparent.
Sprint
Sprint
Plan a Sprint Goal and inspect progress toward it daily.
Increment
Increment
Integrate Done Increments and inspect outcome and environment in Sprint Review.
Adapt
Adapt
Adapt Product Backlog and ways of working in Review and Retrospective.
Update after new evidence or a material context change and retain the previous version.
A good fit when
For complex products with an empowered, cross-functional, self-managing Scrum Team.
Ideal for
- Komplexe Produktentwicklung
- Cross-funktionale Teams
- Iterative Auslieferung
- Lernen pro Sprint
Not good for
- Pure support or maintenance workloads
- Highly regulated waterfall environments
- Very simple linear tasks
Outputs
Scrum operating agreement
Scrum operating agreement with traceable sources, assumptions, and domain decisions.
Decision and review trail
Owners, dates, and next review for Scrum operating agreement.
Scrum operating agreement
Fictional worked example
Sprints with Planning, Daily Scrum, Review, and Retrospective around three artefacts and commitments as a precise working structure with a fictional example.
Accountabilities
Record concrete Accountabilities information for this Scrum instance.
Product Owner Lea orders the Product Backlog toward the Product Goal; Scrum Master Amir coaches Scrum use; Developers Kim, Noor, Eva, and Luis create the Increment.
Events
Record concrete Events information for this Scrum instance.
Two-week Sprint: Planning Monday 09:00; Daily Scrum 09:15; Review Friday 13:00 with Support and Compliance; Retrospective 14:30.
Artefacts/commitments
Record concrete Artefacts/commitments information for this Scrum instance.
Product Goal: find a review decision with evidence in under 30 seconds. Sprint Goal: search by project, owner, and status. Definition of Done: integrated, tested, WCAG 2.2 AA, audit log, and production-ready.
Empirical inspection
Record concrete Empirical inspection information for this Scrum instance.
Review: seven of eight stakeholder tasks under 30 seconds; status filter unclear. Product Backlog receives a terminology test. Retrospective: prepare anonymised test data before Planning.
The example demonstrates the domain logic of Scrum; worksheets remain blank.
First step
Start with the core question: How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?
Good to do first
Deep dive
How it works
It ties planning, daily coordination, review, and improvement to a recurring frame. Roles, events, and artifacts ensure that progress, feedback, and adaptation converge in short cycles.
In detail
Scrum works because the framework couples product goal, short delivery cycles, and regular inspection so that learning and implementation share the same cadence. Good application does not depend on ceremonial correctness but on genuinely maintained backlog work, clear responsibilities, and real willingness to adapt after review and retrospective. Introduced mechanically, Scrum produces calendar discipline; anchored properly, it strengthens focus, transparency, and decision-making capability in everyday team life.
Facilitation
Introduce the framework through concrete everyday problems, such as missing priority, unclear responsibility, or late surprises, so that adoption has a recognizable benefit. The matter becomes really concrete once product goal, backlog, and sprint work visibly fit together for the first time. Close every introduction phase with a few behavioral anchors that are deliberately observed in the next sprint.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Scrum: WorksheetPlan Scrum around its domain steps and the concrete decision question.markdown
Scrum: WorksheetPlan Scrum around its domain steps and the concrete decision question.
markdownscrum-working-template.md
Plan Scrum around its domain steps and the concrete decision question.
Scrum: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Establish and review the practice Time: Continuous; Sprint no longer than one month
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Product Goal and Product Backlog, Definition of Done, empowered Scrum Team, shared workspace, source links, and decision log.
- Roles: Product Owner · Scrum Master · Developers
- Advance information: Collect Product Goal and Product Backlog, Definition of Done, empowered Scrum Team in advance and mark open assumptions.
- Overall time needed: Continuous; Sprint no longer than one month
- Setup: Prepare Sprints with Planning, Daily Scrum, Review, and Retrospective around three artefacts and commitments visibly and calibrate assessment terms before starting.
Prepare for the work steps
Product Goal: Product Goal
- Product Goal and Product Backlog
- Definition of Done
- empowered Scrum Team
Sprint: Sprint
- product backlog
- Definition of Done
- empowered Scrum Team
Increment: Increment
- sprint backlog
- Definition of Done
- empowered Scrum Team
Adapt: Adapt
- Done Increment
- Definition of Done
- empowered Scrum Team
Scrum operating agreement
Accountabilities
Record concrete Accountabilities information for this Scrum instance.
...
Events
Record concrete Events information for this Scrum instance.
...
Artefacts/commitments
Record concrete Artefacts/commitments information for this Scrum instance.
...
Empirical inspection
Record concrete Empirical inspection information for this Scrum instance.
...
Enter only real input, sources, and decisions.
Product Goal: Product Goal
Expected artifact: product backlog
product backlog · source · uncertainty · next decision
Entry:
...
- Does each item support the Product Goal?
Sprint: Sprint
Expected artifact: sprint backlog
sprint backlog · source · uncertainty · next decision
Entry:
...
- Does the Sprint Goal remain stable while the plan adapts?
Increment: Increment
Expected artifact: Done Increment
Done Increment · source · uncertainty · next decision
Entry:
...
- Does the Increment fully meet the Definition of Done?
Adapt: Adapt
Expected artifact: adaptations
adaptations · source · uncertainty · next decision
Entry:
...
- Does adaptation follow observed evidence?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/scrum/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Product Discovery
Dual-Track Agile
Instead of Scrum, choose Dual-Track Agile when you want to deliberately run discovery and delivery in parallel because you need to learn and deliver at the same time.
Agile
Ideal Days
Moves backlog, sprint work, and team flow toward a concrete result through "explain the ideal day unit", "calibrate with a reference item", and "do not confuse it with calendar days".
Agile
T-Shirt Sizing
Sorts backlog items roughly by reference sizes and flags early on which items will later need splitting or clarification.
Agile
NoEstimates
Moves backlog, sprint work, and team flow toward a concrete result through "clarify the planning question", "slice work smaller", and "calibrate regularly with reality".
Agile
Story Points
Moves backlog, sprint work, and team flow toward a concrete result through "choose reference stories", "define the scale", and "interpret velocity only within the team".
Delivery
Shape Up
Structures product work around shaped pitches, bets, fixed cycles, hill charts, and scope hammering.
Constraints and origin
MediumWorkshop + async1-4 Wochen je Sprint, laufend
Profile
- Method form
- Framework
- Participants
- 3-10 (Scrum Team)
- Time
- 1-4 Wochen je Sprint, laufend
- Maturity
- Canonical
- Origin
- Ken Schwaber and Jeff Sutherland
Next up: Sprint Retrospective