View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Agile Ideal Days |  Decision Making PERT Estimation |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-4 h | 15-60 min | 15-45 min | 2-5 min je Item |
Participantsdifferent | 1-5 | 2-9 | 1-8 | 3-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Ideal Day Estimates, Assumption Notes, Capacity Caveats | PERT Estimate, Expected Value, Risk Notes | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | ArchitectureCommunicationVisualization | EstimationEffortAgile | EstimationUncertaintyRisk | EstimationAgileRelative sizingTeam |