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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitysame
LowLow
Timedifferent
45–75 min30 min Setup, dann laufend
Participantsdifferent
Team members involved1-3 maintaining, briefing for everyone
Formatdifferent
WorkshopAsync
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsRAID Log, Status Report Source
Tagsno overlap
RetrospectiveLearningReflectionTeam
RiskTrackingStakeholdersGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping