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 Specification by Example |  Agile Example 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 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 story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | 2-4 h | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 3-12 | 3-12 | 3-6 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Team Charter, Working Norms, Role Notes | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | TeamCollaborationAgile | TeamAlignmentCollaboration | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |