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 Planning Poker |  Facilitation Stakeholder Mapping |  Delivery RAID Log |
|---|---|---|---|
Purposedifferent | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 2-5 min je Item | 60–90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-9 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source |
Tagsno overlap | EstimationAgileRelative sizingTeam | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
