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 |  Agile Planning Poker |  Agile Bucket System |
|---|---|---|---|---|
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 30 min Setup, dann laufend | 2-5 min je Item | 30-90 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-9 | 3-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | RAID Log, Status Report Source | Relative Estimates, Assumption Notes, Split Candidates | Bucketed Backlog, Relative Estimates, Split Candidates |
Tagsno overlap | TeamCollaborationAgile | RiskTrackingStakeholdersGovernance | EstimationAgileRelative sizingTeam | EstimationBacklogRelative sizing |