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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
MediumLowLowHigh
Timedifferent
30-90 min30 min Setup, dann laufend45–75 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-121-3 maintaining, briefing for everyoneTeam members involvedEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Postmortem Doc, Action Items, TimelineRAID Log, Status Report Source4Ls Board, Learning Themes, Improvement ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
RiskTrackingStakeholdersGovernance
RetrospectiveLearningReflectionTeam
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods