View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Quality Attribute Workshop |  Agile Example Mapping |  Innovation Brainstorming |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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 team faces an open question with many obvious directions, the method first creates breadth instead of premature commitment. It separates idea flow from evaluation and makes lines of thought visible, creating a pool for selection and further development. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 30-60 min | 30-60 min | 20-40 min pro Story |
Participantsdifferent | 5-15 | 3-7 | 4-12 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Example Map, Acceptance Criteria, Open Questions | Idea pool, Theme clusters, Shortlist | Acceptance Criteria, Story Update |
Tagsno overlap | RequirementsArchitectureWorkshop | Behavior-Driven DevelopmentRequirementsExamplesRefinement | BrainstormingIdeationCreativityWorkshopDivergence | AgileRequirementsRefinementBehavior-Driven Development |