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 Acceptance Criteria Workshop | ![]() Agile Working Agreements | ![]() Facilitation Team Charter | ![]() Agile Three Amigos |
|---|---|---|---|---|
Purposedifferent | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 20-40 min pro Story | 45-90 min | 2-4 h | 15-30 min |
Participantsdifferent | 3-6 | 3-12 | 3-12 | 3 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Working Agreements, Team Norms, Review Cadence | Team Charter, Working Norms, Role Notes | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | TeamCollaborationAgile | TeamAlignmentCollaboration | CollaborationBehavior-Driven DevelopmentQualityRefinement |



