View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Planning PokerSoftware Architecture CanvasAlignment MappingArchitecture Communication Canvas
| Criterion |  Agile Planning Poker |  Architecture Software Architecture Canvas |  Facilitation Alignment Mapping |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 2-5 min je Item | 1-2 h | 1-2 h | 60-120 min |
Participantsdifferent | 3-9 | 3-10 | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Architecture Canvas, Goals, Constraints, Quality Attributes | Alignment Map, Open Issues, Decision Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | EstimationAgileRelative sizingTeam | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersStrategyFacilitation | ArchitectureCommunicationStakeholdersCanvas |