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 |  Delivery Shape Up |  Architecture arc42 |  Architecture C4 Model |
|---|---|---|---|---|
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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-2 Tage | 1-4 h |
Participantsdifferent | 3-10 | 2-4 pro Pitch | 1-4 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | AutonomyRolesTeam | PlanningDeliveryAutonomy | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |