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 Scrum |  Agile Acceptance Criteria Workshop |  Delivery RAID Log |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 20-40 min pro Story | 30 min Setup, dann laufend |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Acceptance Criteria, Story Update | RAID Log, Status Report Source |
Tagsno overlap | AgileIterationCadence | AgileRequirementsRefinementBehavior-Driven Development | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
