Instilling the built-in quality mindset into a dev team
summary
Content lays out five concrete dimensions—flow, code, release, system and architecture quality—and names specific practices to make them real: test pyramid with unit-first automation, BDD for a shared language, CI/CD pipelines that run on every merge, TDD, code review and a walking skeleton architecture. Claims: quality becomes a byproduct when teams adopt small habits, automate low-value checks, measure baselines and normalize feedback. Practical outcome: incremental wins replace big-bang QA and reduce production defects by catching issues earlier.
AI-written summary · about
chapters (15)
- 0:00Built-in quality mindset intro
- 1:09Quality everyone's responsibility
- 3:58Five dimensions of built-in quality
- 5:01Flow and shift left
- 8:13Code quality and test automation
- 10:19Definition of done and scalable quality
- 11:22Architecture quality principles
- 13:30BDD and CI/CD
- 14:12Steps to instill quality mindset
- 17:45QA feedback loop
- 20:15Test everywhere every time
- 22:00Culture first then tools
- 24:51Leading quality transformation
- 25:54Empathy and team barriers
- 26:58Start with quick wins
related talks
20mEnsuring Quality in DevOps Culture
01h 07mBuilt In Quality Reach Beyond the Team
14mThinking of Quality as developer productivity tool
13mCommitting to quality
42mImproving Testing Quality by Changing Culture
35mWhy Software Engineers Should Make Quality a Priority
28mQuality as an attitude – From Testing to Quality Engineering to…what?
06m“Quality-conscious Software Delivery”