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 |  Operations Getting Things Done |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Weekly 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 30 min Setup, dann laufend | 1-2 h Setup, laufend | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1 | Evaluation team, architects, and relevant stakeholders | 1 |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Action Lists, Project List, Review Routine | 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 |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ProductivityPlanningTasksExecution | ArchitectureQualityRiskTradeoffsStakeholders | ProductivityExecutionPlanning |