delivery

Turns technical problems, assumptions, and next steps into a tangible result through mapping the workflow, making work visible, and improving bottlenecks.

Core question: How does work flow through the stages, where does it queue up, and which policy keeps WIP limits intact?

Ongoing

2-12

Turns scope, sequence, and delivery flow into a tangible result through selecting a value stream, mapping current state, and designing a future state.

Core question: Where do waiting time, rework, and waste emerge between trigger and delivery, and which two or three interventions improve lead time most?

1-3 h

4-10

Turns backlog, sprint work, and team flow into a tangible result by identifying oversized stories, finding the smallest value slice, and reprioritizing.

Core question: How can the story be split into 2-5 slices, each delivering value or learning, without losing overall benefit?

30-60 min

2-6

Turns scope, sequencing, and delivery flow into a tangible result by listing stakeholders and audiences, clarifying information needs, and planning review and adaptation.

Core question: Which message reaches which audience through which channel in which cadence so the initiative is understood, accepted, and supported as planned?

45-90 min

2-6

Moves scope, sequence, and delivery flow toward a concrete result through "formulate the forecast question", "choose historical flow data", and "update the forecast regularly".

Core question: With what probability will the desired scope be finished by the target date (or how much scope can we complete by then), and which assumptions drive the distribution?

30-90 min Setup, danach laufend

1-8

Moves scope, order, and delivery flow toward a concrete result through "adopt the initiative list", "clarify value types for each initiative, such as revenue, efficiency, or risk", and "derive a sorted sequence".

Core question: How much does each week cost us when this initiative is not delivered, and in which order should we maximize avoided loss?

90-180 min

3-8

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?

Laufend, Wochen bis Monate

4-10

Structures product work around shaped pitches, bets, fixed cycles, hill charts, and scope hammering.

Core question: Which shaped pitches do we bet on for the next 6-week cycle, and how does the team deliver them autonomously in fixed time with negotiable scope?

6 Wochen Cycle + 2 Wochen Cool-Down

2-4 pro Pitch