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 Working Agreements |  Delivery RAID Log |  Facilitation Dot Estimation |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 5-20 min | 2-5 min je Item |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-20 | 3-9 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | RAID Log, Status Report Source | Effort Heatmap, Risk Signals, Discussion Targets | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | TeamCollaborationAgile | RiskTrackingStakeholdersGovernance | EstimationEffortRisk | EstimationAgileRelative sizingTeam |