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 Specification by Example |  Agile Sprint Retrospective |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | 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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-40 min pro Story |
Participantsdifferent | 3-6 | Scrum Team | 3-6 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Improvement actions, Team agreements | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RetrospectiveImprovementLearning | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
