QualityStorming: Collaborative Modelling for Quality Requirements
summary
Workshop method that turns vague nonfunctional wishes into a prioritized, actionable set of quality requirements. Uses a quality model such as ISO 25010, eight top categories on pinboards, small mixed groups rotating in 10–20 minute rounds, then consolidation in larger groups, and dot voting with about 15–25 dots to surface priorities. Designed for 16–24 participants, runs in person with sticky notes or remotely on Miro/Mural plus breakout rooms, and produces consolidated, measurable quality scenarios and a basis for architecture trade‑offs.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:52About me
- 8:04What is QualityStorming
- 11:34Selecting a Quality Model
- 16:19Invite the Right People
- 18:24Prepare the Workshop
- 34:24Sticky dots
- 35:54Architecture tradeoffs
- 37:24Qualitystorming in a remote fashion
- 40:06Next steps after the workshop
- 41:54Questions
related talks
33mEvent Storming for Everyone
47mESSENTIALS - Event Storming for fun and profit
50mHow EventStorming Transformed Our Domain Modeling Process
31mHow EventStorming Transformed Our Domain Modeling Process
01h 01mThe art to define and test System Quality Attributes
49mFrom Days to Hours: How EventStorming Transformed Our Domain Modeling Process
41mCollaborative Software Design: How to facilitate domain modeling decisions
01mMike Wojtynac at DDD Europe 2025