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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Paper illustration of KPI Tree with its method-specific working model.
Product Strategy
KPI Tree
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.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.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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 h90-180 min90-180 min initial, dann laufend1-2 h
Participantsdifferent
3-103-63-84-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesGQM Table, Metric ProfilesKPI Tree, Owner ListAlignment Map, Open Issues, Decision Questions
Tags1 shared
CanvasArchitectureAlignmentWorkshop
MetricsMeasurementEngineeringAlignment
MetricsStrategyAlignmentMeasurement
AlignmentStakeholdersStrategyFacilitation
Add more methods