View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  Architecture Architecture Communication Canvas |  Team Design Team API |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 2-4 h | 60-120 min | Half day initial, dann laufend | 1-2 h |
Participantsdifferent | 3-12 | 2-8 | Ein Team plus Stakeholder | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Team API Document | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | TeamAlignmentCollaboration | ArchitectureCommunicationStakeholdersCanvas | TeamAlignmentCommunicationService | CanvasArchitectureAlignmentWorkshop |