Captures experiences over time in diary entries and reveals longitudinal patterns that a single session would miss.
Core question: Which recurring experiences, triggers, and changes appear over time beyond a single session?
Research methodMethod form: Research method. Describes how this method is used in practice.MediumComplexity: medium. Estimates preparation, facilitation effort, and method confidence needed.AsyncFormat: async. Shows whether the method works in a workshop, asynchronously, or both.
1-4 Wochen
5-20
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: How will each relevant risk be treated, and what must happen before the next review?
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
Details
DeliveryCategory: Delivery. Describes the method's domain of use.
Moves scope, sequence, and delivery flow toward a concrete result through "create a table for Risks, Assumptions, Issues, and Dependencies", "carry over initial entries from discovery and kickoff", and "archive resolved items instead of deleting them".
Core question: Which open Risks, Assumptions, Issues, and Dependencies threaten the next commitment, and who will do what by when?
Planning toolMethod form: Planning tool. Describes how this method is used in practice.LowComplexity: low. Estimates preparation, facilitation effort, and method confidence needed.AsyncFormat: async. Shows whether the method works in a workshop, asynchronously, or both.