Never-Neverland of pursuing Quality
summary
Argues that quality is a shared responsibility, not just QA, and gives concrete rules: use a Definition of Ready: acceptance criteria, mockups, team review and a Definition of Done: code, unit tests, peer review, demos so stories don’t waste time; run short-lived feature branches + CI (or feature toggles) and require unit tests and reviews before QA starts; schedule maintenance and code-complete Friday windows; treat test code like production code; keep teams small (≈8) and a dedicated scrum master.
AI-written summary · about
chapters (11)
- 0:00Introduction to quality mindset
- 3:08Agile isn't just following frameworks
- 8:59Backlog mountain practices
- 13:59Backlog maintenance and cleanup
- 16:28Deep dark forest of development
- 21:50Super quick stop at megapolis
- 24:26Automation and test code quality
- 27:54Team park and team culture
- 33:16Quality mindset recap
- 40:44Q&A on emergencies and compromises
- 52:13Closing and thanks
related talks
28mInstilling the built-in quality mindset into a dev team
21mEstablishing Quality Assurance in Startup environment
01h 01mKEYNOTE: The Affordances of Quality
14mThinking of Quality as developer productivity tool
13mCommitting to quality
37mDavy Kenis: QA No More: Revolutionizing Software testing
01h 07mBuilt In Quality Reach Beyond the Team
18mHow to be quick without being dirty: maintaining quality at high velocity