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 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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
45–75 min1-3 Tage30-60 min1-2 Tage
Participantsdifferent
Team members involved1-43-101-4
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsArchitecture Views, Cross-view Notes, RationaleEmotion Board, Themes, Action ItemsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
RetrospectiveLearningReflectionTeam
DocumentationStakeholdersArchitecture
RetrospectiveTeamReflection
ArchitectureDocumentationCommunication
Add more methods