7 ways to go wrong with engineering metrics

The software industry has a long history in using harmful metrics to measure developer productivity.

And that's why in this live session, Swarmia CEO and founder, Otto Hilska, walks through seven ways companies get engineering metrics wrong — and four tips for getting started with healthy metrics that drive positive outcomes.

00:00 Intro
02:09 The 7 anti-patterns in measuring software development productivity
02:40 1. Stack ranking developers
04:28 2. One aggregate metric
05:30 3. The ivory tower approach
06:36 4. One category of metrics
09:46 5. Nonsense metrics (like code churn)
11:14 6. Mixing velocity and predictability
13:33 7. Taking someone else's opinion too literally
15:02 What should you do instead?
15:10 1. Care about continuous improvement
16:46 2. Start with cycle time and WIP limits
20:34 3. Focus on work and learning over metrics
23:02 4. Always be balancing
26:18 Q&A

LINKS
Practical guide to DORA metrics: www.swarmia.com/blog/dora-metrics/
Balancing engineering investments: www.swarmia.com/blog/balancing-engineering-investm…
How to ship software 10x faster: www.swarmia.com/blog/ship-software-10x-faster/
Book a demo: www.swarmia.com/demo/
Start your free 14-day trial: www.swarmia.com/signup/