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 WSJF |  Knowledge Modeling IBIS |  Architecture Request for Comments |  Delivery Cost of Delay |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | High | Medium | Medium | High |
Timedifferent | 45-90 min | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min |
Participantsdifferent | 3-10 | 2-8 | 3-20 Reviewer | 3-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Issue Map, Positions, Argument Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | CoD Table, Prioritization Sequence |
Tagsno overlap | LeanEconomicsSequencePrioritization | RationaleKnowledgeDecision | ArchitectureDecisionAsyncGovernance | PrioritizationDeliveryEconomicsDecision |