View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile T-Shirt Sizing | ![]() Delivery RAID Log | ![]() Decision Making DACI | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 30 min Setup, dann laufend | 30-60 min | 60-90 min |
Participantsdifferent | 2-12 | 1-3 maintaining, briefing for everyone | 2-10 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | RAID Log, Status Report Source | DACI Matrix, Decision Owner, Decision Log | Salience Diagram, Strategy per Class |
Tagsno overlap | EstimationAgileRoadmap | RiskTrackingStakeholdersGovernance | DecisionRolesGovernanceAlignment | StakeholdersFacilitationAlignmentGovernance |



