methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Story Splitting method illustration showing its working structure
Agile
Story Splitting
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Purposedifferent
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.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.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.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
30-90 min30-60 min1-2 Tage1-4 h
Participantsdifferent
3-122-61-41-5
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsSmaller Stories, Acceptance Criteria, Split RationaleArchitecture Document, Context View, Runtime View, Deployment ViewContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
EstimationBacklogRelative sizing
BacklogIterationDelivery
ArchitectureDocumentationCommunication
ArchitectureCommunicationVisualization
Add more methods