View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Working Agreements |  Facilitation Team Charter |  Agile Planning Poker |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 2-4 h | 2-5 min je Item | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | 3-9 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Team Charter, Working Norms, Role Notes | Relative Estimates, Assumption Notes, Split Candidates | Expectation Map, Alignment Notes, Agreements |
Tags1 shared | TeamCollaborationAgile | TeamAlignmentCollaboration | EstimationAgileRelative sizingTeam | AlignmentStakeholdersTeam |