Built In Quality Reach Beyond the Team
summary
Covers a concrete claim: Built‑In Quality requires defined feedback loops across the whole development lifecycle and maturity levels, not just more tests. Explains how to map practices (test‑first TDD/BDD, CI/CD, testing pyramid, shared code ownership, surface virtualization) onto those loops, gives a 75 practices catalog, a definition of ready on epic level, and proposes stop the line (jidoka) + RCA when checks fail. Good for teams and orgs needing actionable patterns, timings, and measurable choices.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:42Business Agility
- 17:53The Testing Pyramid
- 18:43Reduce the Size of the Test Set
- 20:05Scalable Definition of Done
- 23:03Chief Quality Officer
- 25:37Testing Should Be across Team Responsibility
- 27:28Definition of Ready on Epic Level
- 36:41Confessions of a Tester
- 38:27Development Lifecycle
- 49:27The Root Cause Analysis on the Feedback Loop
- 52:48Surfing the Waves of Agile
- 54:41Built in Quality Maturity
- 1:02:28What Areas To Increase and Work on Built-In Quality Are the Most Bang for the Buck
- 1:03:10How Can We Implement Built-In Quality for Large-Scale Migration Project like Migrating an Operating System That Involves Multiple Teams and Features What Approach Can Be Used
- 1:04:45What Are some Examples of Issue Categories for Rca
related talks
28mInstilling the built-in quality mindset into a dev team
14mThinking of Quality as developer productivity tool
43mEnd-to-End Quality
13mCommitting to quality
53mNever-Neverland of pursuing Quality
40mAmplifying Agile Quality Practices
49mIs your Quality on the Road to Nowhere?
46mQuality Engineering for DevOps Teams
