View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking CATWOE Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Mad Sad Glad |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. | When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 30-60 min |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | 3-10 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Emotion Board, Themes, Action Items | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | Systems thinkingFramingStakeholders | ArchitectureQualityRiskTradeoffsStakeholders | RetrospectiveTeamReflection | RetrospectiveImprovementTeamReflection |