methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of Product Kata with its method-specific working model.
Product Discovery
Product Kata
Purposedifferent
When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.Product Kata helps clarify customer problems, solution ideas, and evidence through a repeatable improvement routine. It captures direction, current metric, target metric, experiment notes, and learning.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-4 Wochen je Sprint, laufend20-45 min1-3 h1-2 Wochen je Loop
Participantsdifferent
3-10 (Scrum Team)3-123-103-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalLessons learned, Action items, Event summaryProcess Map, Handoff List, Improvement BacklogDirection, Current metric, Target metric, Experiment note, Learning report
Tagsno overlap
AgileIterationCadence
LearningOperationsImprovement
ProcessOperationsImprovement
OutcomesDiscoveryLearningIterationCoaching
Add more methods