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 Bounded Context Canvas |  Domain Modeling Domain Context Map |  Facilitation Responsibility Poker |
|---|---|---|---|---|
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 a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 1-3 h | 1-3 h | 45-90 min |
Participantsdifferent | 3-10 | 3-8 | 3-10 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Context Canvas, Glossary, Integration Notes | Domain Context Map, Boundary Notes, Ownership Map | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | AutonomyRolesTeam | Domain-Driven DesignBoundariesModeling | Domain-Driven DesignContextBoundaries | RolesResponsibilityTeamFacilitation |