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 NoEstimates |  Business Strategy GAP Analysis |  Architecture arc42 |
|---|---|---|---|
Purposedifferent | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | laufend | 1-3 h | 1-2 Tage |
Participantsdifferent | 2-12 | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | Gap Matrix, Action Plan, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | EstimationForecastingFlow | StrategyAnalysisPlanning | ArchitectureDocumentationCommunication |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
