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 |  Team Design Team API |  Agile ROAM Board |  Agile Working Agreements |
|---|---|---|---|---|
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. | 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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | Half day initial, dann laufend | 20-40 min initial, dann laufend | 45-90 min |
Participantsdifferent | 3-12 | Ein Team plus Stakeholder | 3-15 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Team API Document | ROAM Board, Owner List | Working Agreements, Team Norms, Review Cadence |
Tagsno overlap | TeamAlignmentCollaboration | TeamAlignmentCommunicationService | RiskAgileTrackingAlignment | TeamCollaborationAgile |