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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for DACI
Decision Making
DACI
Purposedifferent
When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
30-60 min30-90 min1-3 Wochen vom Draft bis zur Entscheidung30-60 min
Participantsdifferent
2-63-123-20 Reviewer2-10
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleAffinity Size Map, Grouped Estimates, Unclear ItemsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
BacklogIterationDelivery
EstimationBacklogRelative sizing
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernanceAlignment
Add more methods