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
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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowLowLowMedium
Timedifferent
45–75 min1-2 Tage30-60 min60-120 min
Participantsdifferent
Team members involved1-43-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsArchitecture Document, Context View, Runtime View, Deployment ViewEmotion Board, Themes, Action ItemsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
RetrospectiveLearningReflectionTeam
ArchitectureDocumentationCommunication
RetrospectiveTeamReflection
ArchitectureCommunicationStakeholdersCanvas
Add more methods