methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for RAPID
Decision Making
RAPID
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.With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-4 Wochen je Sprint, laufend45-90 min15-45 min45-90 min
Participantsdifferent
3-10 (Scrum Team)2-81-33-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalRACI Matrix, Responsibility Map, Decision NotesADR File, Decision Log, RationaleRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
AgileIterationCadence
RolesResponsibilityGovernanceOperations
ArchitectureRationaleDocumentationGovernance
DecisionRolesGovernance
Add more methods