Taking Quality to Next Level: Metrics for Improvement
summary
Quality improvement follows concrete practices: wait until testing matures to TMMi level 5 then collect data, run monthly reviews, and act on trends. Metrics come from Jira via its API into a custom dashboard hosted on Azure and visualized with Power BI, or simpler CSV/Excel exports. Teams trial new metrics for about three months, aim for production-bug rate below 5%, track fixed vs open and time-to-fix, and find the custom app with real-time updates reliably surfaces process issues.
AI-written summary · about
chapters (26)
- 0:00Welcome
- 0:48What is TMMI
- 3:19TMMI levels 2 to 5
- 4:44Case study and metrics intro
- 6:31Bug report data fields
- 11:24Root cause analysis fields
- 14:16Bug origin and types
- 16:25Code coverage metrics
- 19:18Implementing quality metrics
- 21:43Avoiding metric misuse
- 23:51Q&A
- 26:01Selling metrics to teams
- 28:09Metric update frequency
- 29:57Choosing relevant metrics
- 32:01Responsibility for data
- 33:04Tools for data collection
- 35:10Top 3 metrics to track
- 35:54Metric calculation sources
- 37:18Trial period for metrics
- 38:01Discarding bad metrics
- 39:27Metrics for team leads
- 40:31Using metrics in discussions
- 41:54Avoiding over-measurement
- 43:18Discussing metrics
- 44:21Bug rate comparison
- 45:02Closing remarks
related talks
14mEssential Metrics for the Quality Assurance
20mHow to Communicate Metrics to Build Engagement
39mTest Metrics – a thread or a threat
24mCan you afford not to improve testing?
26mMetrics and Modeling – Helping Teams See How to Improve
43mTo Measure or Not to Measure? That Is the Question
51mQuality Maturity Model: Driving Excellence In High-Growth Orgs
21mImprove quality by monitoring and observing