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 Scrum |  Agile Example Mapping |  Facilitation Six Thinking Hats |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | When a topic gets stuck too quickly in the same thinking mode, Six Thinking Hats deliberately separates the perspectives. This means facts, risks, creativity, and emotional signals get worked through one after another instead of mixed together. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-60 min | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-7 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Map, Acceptance Criteria, Open Questions | Perspective Notes, Decision Inputs, Action Items |
Tagsno overlap | AgileIterationCadence | Behavior-Driven DevelopmentRequirementsExamplesRefinement | FacilitationOptionsDecision |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
