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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitysame
LowLowLow
Timedifferent
1-4 h1-2 h45–75 min
Participantsdifferent
1-53-10Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Context Diagram, Container Diagram, Component DiagramArchitecture Canvas, Goals, Constraints, Quality Attributes4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ArchitectureCommunicationVisualization
CanvasArchitectureAlignmentWorkshop
RetrospectiveLearningReflectionTeam
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue