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?
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)
Details
Business StrategyCategory: Business Strategy. Describes the method's domain of use.
Connects strategy development, translation, operational planning, monitoring, and adjustment into a repeatable leadership cycle.
Core question: How do we close the loop from strategy through operations to learning and adaptation?
Process modelMethod form: Process model. Describes how this method is used in practice.HighComplexity: high. Estimates preparation, facilitation effort, and method confidence needed.Workshop + asyncFormat: workshop or async. Shows whether the method works in a workshop, asynchronously, or both.
Initial 3-6 h, then monthly or quarterly reviews
5-12
Details
Business StrategyCategory: Business Strategy. Describes the method's domain of use.
Separates planning levels by time horizon, decision type, and control logic, so strategy does not get mixed up with day-to-day business.
Core question: How is strategic direction translated into tactical capabilities and operational work without losing feedback?
Planning toolMethod form: Planning tool. 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.