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 |  Agile Example Mapping |  Innovation Lotus Blossom |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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 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 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30-60 min | 45-90 min | 20-40 min pro Story |
Participantsdifferent | 3-12 | 3-7 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Example Map, Acceptance Criteria, Open Questions | Lotus Diagram, Idea Themes, Shortlist | Acceptance Criteria, Story Update |
Tagsno overlap | TeamCollaborationAgile | Behavior-Driven DevelopmentRequirementsExamplesRefinement | BrainstormingIdeationCreativityDivergenceWorkshop | AgileRequirementsRefinementBehavior-Driven Development |