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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Purposedifferent
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 is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.
Complexitydifferent
LowLowHighLow
Timedifferent
30 min Setup, dann laufendUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorterSeveral meetings plus preparation and analysis; total effort depends on scope20-45 min
Participantsdifferent
1-3 maintaining, briefing for everyoneScrum TeamEvaluation team, architects, and relevant stakeholders3-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceImprovement actions, Team agreementsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsLessons learned, Action items, Event summary
Tagsno overlap
RiskTrackingStakeholdersGovernance
RetrospectiveImprovementLearning
ArchitectureQualityRiskTradeoffsStakeholders
LearningOperationsImprovement
Add more methods