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 for Working Agreements.
Agile
Working Agreements
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 Planning Poker.
Agile
Planning Poker
Purposedifferent
When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths.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.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.
Complexitydifferent
LowMediumLowLow
Timedifferent
45-90 min1-3 h30-120 min2-5 min je Item
Participantsdifferent
3-123-102-63-9
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Working Agreements, Team Norms, Review CadenceProcess Map, Handoff List, Improvement BacklogObservation Notes, Improvement IdeasRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
TeamCollaborationAgile
ProcessOperationsImprovement
LeanObservationProcessOperations
EstimationAgileRelative sizingTeam
Add more methods