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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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 for Starfish Retrospective
Agile
Starfish Retrospective
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.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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.
Complexitysame
LowLowLowLow
Timedifferent
1-2 Tage15-45 min30-60 min45-90 min
Participantsdifferent
1-41-33-124-12
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, RationaleStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods