View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  Agile Specification by Example |  Agile Sprint Retrospective |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 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 | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | 60-90 min pro Feature | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-60 min |
Participantsdifferent | 3-10 | 3-6 | Scrum Team | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Example Table, Acceptance Tests | Improvement actions, Team agreements | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ProcessOperationsImprovement | AgileRequirementsExamplesBehavior-Driven Development | RetrospectiveImprovementLearning | Behavior-Driven DevelopmentRequirementsExamplesRefinement |