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 |  Domain Modeling Context Map |  Agile Start Stop Continue |  Agile Starfish 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-3 h | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 | 2-8 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Context Map, Integration Patterns, Boundary Notes | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | AutonomyRolesTeam | Domain-Driven DesignBoundariesStrategy | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |