Complete firstBounded subject
The scope and purpose of Scrum are stated as a concrete question.
Without scope, Scrum operating agreement becomes arbitrary.
Method guideAgile
Scrum
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
Time1-4 Wochen je Sprint, laufend
Participants3-10 (Scrum Team)
FormatWorkshop + async
MaturityCanonical
01
Prerequisite
What needs to be finished first
Complete firstAccess to relevant perspectives
Product Goal and Product Backlog, Definition of Done, empowered Scrum Team and domain decision makers are available.
Without these perspectives, central claims in Scrum operating agreement remain unsupported.
02
Preparation
What needs to be ready before start
Materials
Product Goal and Product Backlog, Definition of Done, empowered Scrum Team, shared workspace, source links, and decision log.
People / roles
Product Owner · Scrum Master · Developers
Pre-read
Collect Product Goal and Product Backlog, Definition of Done, empowered Scrum Team in advance and mark open assumptions.
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.
03
Core question
The one question this method answers
How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?
04
Flow
Phases with goal, actions, output and pitfall
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.
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.
- 1
Product Goal
Product Goal
Goal
Produce product backlog so the core question “How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?” can be answered with stronger support.
Inputs for this step
- Product Goal and Product Backlog
- Definition of Done
- empowered Scrum Team
Actions
- Make Product Goal and ordered Product Backlog transparent.
- Record source, rationale, and open uncertainty directly in product backlog.
Output
product backlog
product backlog · source · uncertainty · next decision
Quality check
Does each item support the Product Goal?
Pitfall
Events become status meetings or unfinished work is called an Increment despite the Definition of Done. Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
Timing: 10–20 minutes
- 2
Sprint
Sprint
Goal
Produce sprint backlog so the core question “How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?” can be answered with stronger support.
Inputs for this step
- product backlog
- Definition of Done
- empowered Scrum Team
Actions
- Plan a Sprint Goal and inspect progress toward it daily.
- Record source, rationale, and open uncertainty directly in sprint backlog.
Output
sprint backlog
sprint backlog · source · uncertainty · next decision
Quality check
Does the Sprint Goal remain stable while the plan adapts?
Pitfall
Events become status meetings or unfinished work is called an Increment despite the Definition of Done. Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
Timing: 10–20 minutes
- 3
Increment
Increment
Goal
Produce Done Increment so the core question “How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?” can be answered with stronger support.
Inputs for this step
- sprint backlog
- Definition of Done
- empowered Scrum Team
Actions
- Integrate Done Increments and inspect outcome and environment in Sprint Review.
- Record source, rationale, and open uncertainty directly in Done Increment.
Output
Done Increment
Done Increment · source · uncertainty · next decision
Quality check
Does the Increment fully meet the Definition of Done?
Pitfall
Events become status meetings or unfinished work is called an Increment despite the Definition of Done. Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
Timing: 10–20 minutes
- 4
Adapt
Adapt
Goal
Produce adaptations so the core question “How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?” can be answered with stronger support.
Inputs for this step
- Done Increment
- Definition of Done
- empowered Scrum Team
Actions
- Adapt Product Backlog and ways of working in Review and Retrospective.
- Record source, rationale, and open uncertainty directly in adaptations.
Output
adaptations
adaptations · source · uncertainty · next decision
Quality check
Does adaptation follow observed evidence?
Pitfall
Events become status meetings or unfinished work is called an Increment despite the Definition of Done. Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
Timing: 10–20 minutes
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
Versioned Scrum operating agreement with date, sources, owners, and next review.
Versioning / ownership
Retain date, source, assumption state, and decision for every version of Scrum operating agreement.
Tool alternatives
- Scrum operating agreement as board or document
- Source and evidence register
- Decision and action log
scrum-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
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
scrum-beispiel.md
Concrete filled scenario, fictional example
Product Goal: teams can retrieve decisions with evidence. Sprint Goal: find a saved decision in under 30 seconds. Increment meets the Definition of Done including accessibility and audit log. Review inspects usage with stakeholders; Retrospective improves test-data flow.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Product GoalEvents become status meetings or unfinished work is called an Increment despite the Definition of Done.View in phase
- SprintEvents become status meetings or unfinished work is called an Increment despite the Definition of Done.View in phase
- IncrementEvents become status meetings or unfinished work is called an Increment despite the Definition of Done.View in phase
- AdaptEvents become status meetings or unfinished work is called an Increment despite the Definition of Done.View in phase
Trap
Product Goal
Symptom
Events become status meetings or unfinished work is called an Increment despite the Definition of Done.
What to do
Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
Trap
Sprint
Symptom
Events become status meetings or unfinished work is called an Increment despite the Definition of Done.
What to do
Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
Trap
Increment
Symptom
Events become status meetings or unfinished work is called an Increment despite the Definition of Done.
What to do
Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
Trap
Adapt
Symptom
Events become status meetings or unfinished work is called an Increment despite the Definition of Done.
What to do
Realign event purposes, accountabilities, and artefact commitments with the Scrum Guide.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
Scrum operating agreement answers the core question with traceable evidence or explicitly marked uncertainty.
Owners, next actions, and review dates are named for open points.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.