Estimation

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

Has the team group items silently, discusses deviations, and produces consistent relative size pictures.

Core question: How can the team quickly order many comparable items by relative size and discuss only genuine uncertainty?

• 30-90 min
• 3-12

Moves options, criteria, and risks toward a concrete result through "clarify the estimate object and unit", "collect independent estimates", and "document another round and the outcome".

Core question: What estimate range emerges when experts first estimate independently, compare assumptions anonymously, and re-estimate with new information?

• 1-4 h or multiple rounds
• 4-12 Experten

Moves options, criteria, and risks toward a concrete result through "clarify the estimate object", "determine the optimistic value", and "derive the range, expected value, and risks".

Core question: What range and triangular expected value follow from a plausible optimistic, most likely, and pessimistic scenario?

• 10-30 min je Item
• 1-8

Moves options, criteria, and risks toward a concrete result through "collect three values", "explain the formula", and "document the planning assumption".

Core question: What PERT expected values and variances follow from O/M/P, and how are independent work packages aggregated correctly?

• 15-45 min
• 1-8

Moves backlog, sprint work, and team flow toward a concrete result through "prepare buckets and scale", "place reference items", and "flag large or unclear items".

Core question: Which relative size bucket fits each item when the team places in parallel, corrects once, and separates genuine conflicts?

• 30-90 min
• 3-12

Moves group input, selection, and decision toward a concrete result through "make items visible", "clarify what the dots mean", and "discuss large or risky items".

Core question: Where does each person independently place an item on the same relative size lane, and which dot spread reveals different models of the work?

• 5-20 min
• 3-20

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 "clarify the planning question", "slice work smaller", and "calibrate regularly with reality".

Core question: How can the team make planning and delivery decisions with small work items, flow data, and frequent reforecasting without estimating every item upfront?

• laufend
• 2-12