Engineering Intelligence via Engineering Metrics
summary
Four metric categories drive the pitch: delivery, quality, developer experience and operational data, collected from GitHub, CI, SonarQube and Jira and fed into Engineering Intelligence Platforms with ~30 ready integrations. A real project shows test coverage up → time-to-market down and lower defect density after adding automated tests; DORA-style delivery metrics (lead time, deploy frequency, MTTR) and cloud cost per customer reveal where to cut waste. Start small, automate collection, measure at team level, and avoid cross‑project comparisons.
AI-written summary · about
chapters (10)
- 0:00Engineering Intelligence intro
- 1:08Engineering team challenges
- 5:06Business intelligence for engineering
- 8:18Four engineering metrics categories
- 15:21Leading vs lagging indicators
- 20:24Building intelligence from metrics
- 26:20Test coverage real-world impact
- 32:07Pitfalls and double-edged nature of metrics
- 37:26Engineering intelligence for business
- 39:56Resources and closing
related talks
26mEngineering metrics, minus the creepiness
44mEnhancing the Performance of Engineering Teams
18mFrom developer productivity to engineering impact
10mAchieving engineering velocity by optimising developer experience
29mYour Metrics Are Lying: How to Stop Reporting and Start Learning
33mMeasuring Developer Efficiency in DevOps: Key Questions, Metrics, Best Practices
33mBeyond developer productivity: what's next?
39mDev Team Metrics that Matter