Quality Begins With Requirements
summary
Claim: quality starts with better requirements and that following a compact set of practices prevents most expensive rework. Recommends 20 core practices grouped into foundation, elicitation (use cases, event analysis, data modeling), analysis (modeling, prioritization), specification (glossary, decision tables), validation (peer reviews, inspections, write tests from first requirement) and management (baselines and change control). Cites surprising feature waste estimates of 50–80% unused and treats traceability as the essential 21st practice to link requirements to design, tests and releases.
AI-written summary · about
chapters (15)
- 0:00Welcome and theme
- 2:11Quality begins with requirements
- 3:36Requirements rework causes
- 8:5120 core requirements practices
- 10:14Foundation for success
- 13:04Business objectives early
- 16:58Requirements elicitation techniques
- 21:15Usage-centric approach
- 26:08Quality attributes and expectations
- 29:43Requirements analysis and modeling
- 39:18Requirements specification
- 47:05Requirements validation
- 50:18Peer reviews for requirements
- 57:22Requirements management
- 59:29Summary
related talks
01h 07mBuilt In Quality Reach Beyond the Team
28mInstilling the built-in quality mindset into a dev team
56mControlling Quality in Software Development
45mPanel Discussion | How to deal with bad requirements in testing?
43mEnd-to-End Quality
13mCommitting to quality
53mNever-Neverland of pursuing Quality
46mQuality Engineering for DevOps Teams