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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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.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 complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-4 Wochen je Sprint, laufend30-120 min45-90 min1-3 h
Participantsdifferent
3-10 (Scrum Team)2-62-53-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalObservation Notes, Improvement IdeasA3 Report, Action Plan, Root Cause AnalysisProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
AgileIterationCadence
LeanObservationProcessOperations
LeanProblem solvingCoachingOperations
ProcessOperationsImprovement
Add more methods