Putting the Q in DevEx
summary
QA maps concrete actions to DORA metrics and shows how test work changes those numbers: deployment frequency, lead time for change, change failure rate, mean time to recovery. Claims include that test automation (pyramid, parallel execution), shift‑left practices and continuous testing shorten lead time and raise deploy cadence, while chaos/recovery exercises shrink MTTR. DORA is owned by Google since 2018 and teams report change failure rate to prove impact; a grocery startup example appears.
AI-written summary · about
chapters (7)
- 0:00Introduction to DevEx
- 1:08DevEx history and relevance
- 8:14What DevEx means
- 11:52Dora metrics in DevEx
- 16:09QA role in DevEx
- 23:11QA takeaways for DevEx
- 25:19Q&A
related talks
14mSmarter #Testing for Better Speed & #Quality with DORA Metrics
37mCI/CD Observability, Metrics and DORA: Shifting Left and Cleaning Up!
22mDev Team Metrics that Matter
39mDev Team Metrics that Matter
46mDORA, CSA, AI Act - What Does All of This Mean to Me as a Tester?
47mHow Testing is Evolving in DevOps
44mDefining “DevExT”, the Developer Experience in Testing
30mDevEx and Productivity Metrics on Backstage - Do's and Don'ts