Agile

Jointly formulates valid working rules and clarifies how the team handles expectations, conflicts, and reviews.

Core question: Which observable agreements help this team collaborate reliably and respectfully?

• 45-90 min
• 3-12

Compares stories relatively, surfaces knowledge gaps, and produces a shared estimate with traceable assumptions.

Core question: Which relative size can the delivery team support after independent selection, simultaneous reveal, and clarification of the highest and lowest assumptions?

• 2-5 min je Item
• 3-9

Sorts backlog items roughly by reference sizes and flags early on which items will later need splitting or clarification.

Core question: Which rough relative size class describes each comparable item using shared anchors without false precision or hidden point conversion?

• 15-45 min
• 2-12

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 uninterrupted workdays does an item require under explicit ideal conditions, and which real calendar factors are planned separately?

• 15-60 min
• 2-9

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 an item relative to known team stories when effort, complexity, and risk are considered together without translating points into hours?

• laufend, 1-5 min je Item
• 3-9

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: How will each relevant risk be treated, and what must happen before the next review?

• 20-40 min initial, dann laufend
• 3-15

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 show that the business rule is correctly, completely, and testably understood?

• 60-90 min pro Feature
• 3-6

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 rules and examples must hold for this story to be accepted from a business perspective?

• 20-40 min pro Story
• 3-6

Existing vocabularies become reusable term candidates with ownership, versioning, and maintenance decisions attached.

Core question: How do we publish each term stably, understandably, linked, and versionable?

• Wochen bis Monate
• 2-8

Product Backlog, Sprint Goal, Increment, and retrospective loops create a repeatable cadence for complex product work.

Core question: How does the Scrum Team create a usable Increment every Sprint and learn from outcome and ways of working?

• 1-4 Wochen je Sprint, laufend
• 3-10 (Scrum Team)

Separates discovery and delivery so that validated stories only move into implementation after learning loops.

Core question: Which solution is valuable, usable, feasible, and viable enough for delivery?

• Laufend, Wochen bis Monate
• 4-10