View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Delegation Poker |  Operations Process Mapping |  Agile 4Ls Retrospective |
|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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 a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 45–75 min |
Participantsdifferent | 3-10 | 3-10 | Team members involved |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Process Map, Handoff List, Improvement Backlog | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | AutonomyRolesTeam | ProcessOperationsImprovement | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
