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 |  Agile Three Amigos |  Agile Specification by Example |  Facilitation Team Charter |
|---|---|---|---|---|
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 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 business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | Medium | Medium |
Timedifferent | 45-90 min | 15-30 min | 60-90 min pro Feature | 2-4 h |
Participantsdifferent | 3-12 | 3 | 3-6 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests | Team Charter, Working Norms, Role Notes |
Tagsno overlap | TeamCollaborationAgile | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development | TeamAlignmentCollaboration |