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 for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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
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'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.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 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
LowLowLowLow
Timedifferent
1-2 Tage30-60 min30-60 min45–75 min
Participantsdifferent
1-43-103-12Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewEmotion Board, Themes, Action ItemsStart Stop Continue Board, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ArchitectureDocumentationCommunication
RetrospectiveTeamReflection
RetrospectiveImprovementTeamReflection
RetrospectiveLearningReflectionTeam
Add more methods