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 arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.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.When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage30-60 min15-45 min30-60 min
Participantsdifferent
1-43-121-33-10
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewStart Stop Continue Board, Improvement ActionsADR File, Decision Log, RationaleEmotion Board, Themes, Action Items
Tagsno overlap
ArchitectureDocumentationCommunication
RetrospectiveImprovementTeamReflection
ArchitectureRationaleDocumentationGovernance
RetrospectiveTeamReflection
Add more methods