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 for Risk Storming.
Architecture
Risk Storming
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Purposedifferent
Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list.
Complexitydifferent
LowMediumLowMedium
Timedifferent
60-90 min90-180 min1-2 h90-180 min initial, dann laufend
Participantsdifferent
4-123-63-103-8
Formatdifferent
WorkshopWorkshopWorkshopWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogGQM Table, Metric ProfilesArchitecture Canvas, Goals, Constraints, Quality AttributesKPI Tree, Owner List
Tagsno overlap
RiskArchitectureWorkshopValidation
MetricsMeasurementEngineeringAlignment
CanvasArchitectureAlignmentWorkshop
MetricsStrategyAlignmentMeasurement
Add more methods