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 |  Innovation Lotus Blossom |  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 central question feels too large, the method breaks it into neighboring topic fields with their own depth of ideation. It holds structure and openness at the same time, so adjacent perspectives don't get lost. This grows an idea space out of a core problem. | 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 | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 3-12 | 3-10 | 3-6 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Lotus Diagram, Idea Themes, Shortlist | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | TeamCollaborationAgile | BrainstormingIdeationCreativityDivergenceWorkshop | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |