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 Story Splitting |  Architecture Architecture Decision Record |  Agile Affinity Estimation |  Architecture Request for Comments |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min | 15-45 min | 30-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-6 | 1-3 | 3-12 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | ADR File, Decision Log, Rationale | Affinity Size Map, Grouped Estimates, Unclear Items | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | BacklogIterationDelivery | ArchitectureRationaleDocumentationGovernance | EstimationBacklogRelative sizing | ArchitectureDecisionAsyncGovernance |