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 | ![]() Agile Three Amigos | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 2-4 h | 15-30 min | 60–90 min |
Participantsdifferent | 3-12 | 3 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Team Charter, Working Norms, Role Notes | Clarified Story, Test Examples, Open Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | TeamAlignmentCollaboration | CollaborationBehavior-Driven DevelopmentQualityRefinement | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






