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 Specification by Example |  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 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 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Perspective Notes, Decision Inputs, Action Items |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | FacilitationOptionsDecision |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
