Product Backlog, Sprint Goal, Increment, and retrospective loops create a repeatable cadence for complex product work.
Core question: Which incrementally deliverable, valuable Sprint Goal will the team pursue in the next 1-4 weeks, and how will it adapt its approach based on sprint results?
FrameworkMethod form: Framework. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
1-4 Wochen je Sprint, laufend
3-10 (Scrum Team)
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
Turns backlog, sprint work, and team flow into a tangible result by presenting the item, clarifying questions, and discussing deviations before estimating again.
Core question: How large is this item relative to our reference stories, and which assumptions or risks drive variance within the group?
Decision methodMethod form: Decision method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
2-5 min je Item
3-9
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
Moves backlog, sprint work, and team flow toward a concrete result through "briefly present the story or feature", "collect examples rule by rule", and "hand over the examples as acceptance tests".
Core question: Which concrete examples describe the business logic unambiguously enough to serve as executable tests?
Workshop methodMethod form: Workshop method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
60-90 min pro Feature
3-6
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
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".
Core question: How large is this item relative to our reference stories, considering scope, complexity, risk and uncertainty?
Decision methodMethod form: Decision method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
laufend, 1-5 min je Item
3-9
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
Turns team flow, expectations, and delivery rhythm into a tangible result by clarifying work context, collecting expectations, and setting a review cadence.
Core question: Which concrete behavior expectations make collaboration easier, and which of them does the team want to commit to?
Operating practiceMethod form: Operating practice. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
45-90 min
3-12
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
Moves backlog, sprint work, and team flow toward a concrete result through "pin the story summary to the whiteboard", "write the happy path as Given-When-Then", and "copy the criteria into the story tool".
Core question: Which concrete, testable criteria describe the happy path, edge cases, and negative paths of this story so clearly that all three roles share the same Definition of Done?
Workshop methodMethod form: Workshop method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.WorkshopFormat: workshop. Shows whether the method works in a workshop, asynchronously, or both.
20-40 min pro Story
3-6
Run sheet · visual · session plan
Details
Product DiscoveryCategory: Product Discovery. Describes the method's domain of use.
Verbindet kontinuierliche Product Discovery mit laufender Delivery, damit Teams lernen und liefern, ohne beides zu vermischen.
Core question: Which assumption does Discovery test in this sprint, which validated story enters Delivery, and how is handoff between both tracks kept continuous?
Process modelMethod form: Process model. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
Laufend, Wochen bis Monate
4-10
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
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".
Core question: How many ideal days are needed for this item under focused work, and what assumptions about interruptions, dependencies, and uncertainty are made?
Decision methodMethod form: Decision method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
15-60 min
2-9
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
Moves backlog, sprint work, and team flow toward a concrete result through "create a board with the four columns Resolved, Owned, Accepted, Mitigated", "carry over risks from earlier stages such as Risk Storming", and "update the board at every review".
Core question: Which risks are in which follow-up state, who is responsible, and which need movement between columns now?
Decision methodMethod form: Decision method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
20-40 min initial, dann laufend
3-15
Run sheet · visual · session plan
Details
AgileCategory: Agile. Describes the method's domain of use.
Turns backlog, sprint work, and team flow into a tangible result by explaining the scale, choosing reference items, and marking large items.
Core question: Which size class does each item fall into relative to our references, and which items are so large that they must be cut before planning?
Decision methodMethod form: Decision method. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
15-45 min
2-12
Run sheet · visual · session plan
Details
Knowledge ModelingCategory: Knowledge Modeling. Describes the method's domain of use.
Existing vocabularies become reusable term candidates with ownership, versioning, and maintenance decisions attached.
Core question: How does the team deliver the ontology in iterative, releasable increments that cover Competency Questions and are usable by consumers?
Process modelMethod form: Process model. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.