Test Metrics – a thread or a threat
summary
Slides compare metrics across waterfall and agile, using defect trend chart, defect detection percentage (DDP), defect severity index, and SLA bug-fix times (critical one day, high three days). Claim: single metrics mislead so every metric needs a confirming counterpart. Tools: Excel with light automation. Numbers and practices: six three‑week sprints, severity weights 4/3/2/1, logging defect solving time. Result: integration failures get exposed, offshore transparency improves, and release quality steadies when metrics drive process changes rather than finger‑pointing.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:30Presentation
- 2:10Introduction
- 3:07What are metrics
- 5:08Why use metrics
- 7:02Measuring is power
- 10:42The Vmodel
- 12:43The Advanced Level
- 15:32The Threat
- 21:15Agile vs Waterfall
- 25:12Defect trance chart
- 27:24Defect severity index
- 27:57Critical severity index
related talks
43mTo Measure or Not to Measure? That Is the Question
14mEssential Metrics for the Quality Assurance
01h 01mFinding Metrics that matter and using them safely
29mYour Metrics Are Lying: How to Stop Reporting and Start Learning
26mMetrics and Modeling – Helping Teams See How to Improve
28mMetrics that Matter
59mDevSecOps Productivity Metrics and Tools
06mDelivery Metrics: the good, the bad, and the totally ridiculous