View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Agile Working Agreements |  Agile Planning Poker |  Facilitation Team Charter |
|---|---|---|---|---|
Purposedifferent | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | Half day initial, dann laufend | 45-90 min | 2-5 min je Item | 2-4 h |
Participantsdifferent | Ein Team plus Stakeholder | 3-12 | 3-9 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Team API Document | Working Agreements, Team Norms, Review Cadence | Relative Estimates, Assumption Notes, Split Candidates | Team Charter, Working Norms, Role Notes |
Tags1 shared | TeamAlignmentCommunicationService | TeamCollaborationAgile | EstimationAgileRelative sizingTeam | TeamAlignmentCollaboration |