Engineering metrics, minus the creepiness
summary
Engineering metrics pair industry frameworks like DORA and SPACE with repo data to surface concrete problems: a Multitudes pipeline that hooks into Git shows a lone woman on a team getting far fewer code reviews, prompting redistributed feedback and coaching. Day-to-day rules are specific: use metrics as conversation starters, give teams access and buy‑in, never rank individuals, and track wellbeing via out-of-hours commits and light pulse checks. Incident timing requires agreed start/stop norms to make time‑to‑restore meaningful.
AI-written summary · about
chapters (9)
- 0:00Prae introduces Jenny
- 1:17Jenny introduces herself and her talk
- 5:44What makes up a strong team culture?
- 8:00Engineering metrics
- 14:12How to use metrics day-to-day
- 18:21Summary
- 20:15Audience question: Are there any tools that can easily hook into a repo, and give these metrics?
- 22:57Audience question: How do you measure teams well-being without constant surveys?
- 24:19Audience question: How do you get the context behind the metrics?
related talks
46mEngineering Intelligence via Engineering Metrics
06mDelivery Metrics: the good, the bad, and the totally ridiculous
25mRethinking measurement for high-performing teams
44mEnhancing the Performance of Engineering Teams
41mRethinking Measurement for High-Performing Teams
16mScott Carey & Rebecca Murphey at LeadDev West Coast 2023
20mHow to Communicate Metrics to Build Engagement
15mDev Team Metrics that Matter