View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Weekly Review |  Operations Getting Things Done |
|---|---|---|---|---|
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. | 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. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 1-2 h Setup, laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders | 1 | 1 |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | RAID Log, Status Report Source | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Updated Task System, Weekly Focus, Next Actions | Action Lists, Project List, Review Routine |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders | ProductivityExecutionPlanning | ProductivityPlanningTasksExecution |