Quality Transformation
summary
Quality means shipping a product on time and on budget that meets stakeholder expectations, so QA moves from end‑of‑line inspection to being managed from the start. The practical work is release orchestration—automated tools (Kubernetes, Ansible, monitoring, even Excel spreadsheets) wired into visible feedback loops—so builds, chaos tests and defects feed planning. A value stream map often reveals weeks of delay between reviews and planning. Argues to treat DevOps and CI/CD as intangible assets to justify investment and fix measurement, testing and scheduling failures.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 7:02Quality Assurance
- 8:56Release Orchestration
- 11:06Tools
- 12:31Workflows
- 14:07Middle level managers
- 15:18Testing
- 16:12Everything has to be visible
- 16:54Lack of practical definition
- 20:39Quiz
- 21:09Paying Down Technical Debt
- 22:34Cultural Resistance
- 24:15Value Stream Mapping
- 25:47Delivery Pipeline
- 26:37Software Development Lifecycle
- 29:54Human Development
- 33:49Intangible Assets
- 36:16Challenges
- 39:42Conclusion
related talks
20mEnsuring Quality in DevOps Culture
07m“Importance of Quality Assurance to a delivery team”
53mIs having a QA a symptom of a dysfunctional team?
06mDoes QA have a place in DevOps? Heck yeah!
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
45mWhat Would You Say You Do Here? Reframing Your Role In The QA Field
10mQuality Assistance vs Quality Assurance
22mQualityOps–Left Shift Customer Success With A Thriving Quality Engineering Ecosystem