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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Kaizen Event.
Operations
Kaizen Event
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.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.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-4 Wochen je Sprint, laufend1-3 h30-120 min0.5-5 Tage
Participantsdifferent
3-10 (Scrum Team)3-102-64-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalProcess Map, Handoff List, Improvement BacklogObservation Notes, Improvement IdeasKaizen Charter, Waste List, Improvement Experiments, Standard Work Update
Tagsno overlap
AgileIterationCadence
ProcessOperationsImprovement
LeanObservationProcessOperations
LeanContinuous improvementOperations
Add more methods