View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Monte Carlo Forecasting |  Decision Making Delphi Method |  Architecture Architecture Decision Record |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | 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. | 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 | High | High | Low | Medium |
Timedifferent | 30-90 min Setup, danach laufend | 1-4 Wochen | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-8 | 6-30 Experten | 1-3 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Expert Forecast, Consensus Range, Assumption Notes | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ForecastingFlowDelivery | ForecastingExpertsDecisionStrategy | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance |