> Markdown version of [/videos/1025-do-you-know-how-fast-you-were-developing?t=317](https://www.wearedevelopers.com/videos/1025-do-you-know-how-fast-you-were-developing?t=317). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Do you know how fast you were developing? Optimizing for developer happiness is the ultimate productivity driver. Learn how to ditch gamified metrics and build high-performing engineering teams using the SPACE framework. - **Speakers:** [Markus Walker](https://www.wearedevelopers.com/@markus-walker) - **Event:** World Congress 2024 - **Published:** August 20, 2024 - **Duration:** 25:42 - **URL:** https://www.wearedevelopers.com/videos/1025-do-you-know-how-fast-you-were-developing ## Summary The shift from opaque waterfall processes to iterative agile and devops methodologies has fundamentally changed how engineering teams operate, highlighting the critical need for accurate productivity measurement. Tracking performance helps identify bottlenecks, prevent developer frustration, and inform continuous improvement by comparing teams against their own historical data. However, organizations must avoid common metric pitfalls—like comparing vastly different teams or gamifying targets, which invokes Goodhart's law and leads to counterproductive behaviors such as paying for intentional bugs or incentivizing inflated lines of code. While the industry-standard DORA metrics (deployment frequency, lead time for changes, change failure rate, and time to restore) provide a strong baseline, they often fail to fit highly regulated environments like finance or aeronautics. To capture a more holistic view of engineering health, the SPACE framework incorporates satisfaction, performance, activity, communication, and efficiency. This multidimensional approach recognizes that raw output is heavily correlated with workplace satisfaction and minimal workflow friction. Successfully deploying these frameworks requires establishing clear, transparent goals aligned with all stakeholders while closely monitoring for metric interferences, such as balancing rapid deployments with high-quality pull request reviews. Organizations should ruthlessly eliminate everyday developer frustrations like long build times, inequitable meeting speaking time, and unnecessary context switching caused by reopened tasks. Ultimately, the most actionable insight for engineering leadership is simple: optimizing for developer happiness naturally breeds sustainable, high-performing software teams. **Keywords:** developer productivity tracking, devops continuous measurement, agile burndown charts, dora metrics, space framework, software deployment frequency, change failure rate measurement, engineering team performance, developer context switching, goodhart's law engineering, pull request workflow bottlenecks, build time optimization, developer satisfaction surveys, metrics incentivization pitfalls, quantitative productivity measurement, software quality incentives, engineering leadership insights ## Chapters 1. **Evolution of software measurement from waterfall to agile** (00:50) — Transitioning to agile adoption provides faster feedback cycles to correct the opaque delivery timelines of traditional waterfall methodologies. 1. **Relying on data to identify and prevent development problems** (02:59) — A closed DevOps feedback cycle provides continuous operational data to identify delivery bottlenecks before they disrupt users. 1. **Avoiding harmful team comparisons and metric incentivization** (05:17) — Using productivity metrics as performance targets incentivizes destructive behavior like introducing intentional bugs or padding code volume. 1. **Industry standards and the limitations of DORA metrics** (08:42) — While tracking delivery speed is broadly helpful, universal metrics fail to accommodate the deployment limitations of highly regulated industries. 1. **Applying the SPACE framework for holistic developer productivity** (11:21) — True productivity insights require evaluating developer satisfaction, system performance, and collaboration patterns rather than relying on raw code output. 1. **Defining transparent goals and aligning cross-functional teams** (13:34) — Effective measurement programs require unifying transparent technical goals while ensuring new reporting targets do not degrade job satisfaction. 1. **Selecting targeted technical and cultural performance metrics** (16:39) — Analyzing pull request latency, context-switching rates, and unbalanced meeting participation uncovers the hidden organizational barriers degrading engineering focus. 1. **Implementing regular measurement scopes and evaluation cycles** (20:39) — Integrating progress metrics successfully relies on scoping specific qualitative datasets and discussing root causes before imposing preemptive solutions. 1. **Core takeaways for sustaining long-term developer productivity** (24:34) — Fostering intrinsic developer happiness and continuous transparency yields sustainable system release cycles far better than artificially increasing team headcount. ## Related Moments - [Evolving beyond DORA metrics for software delivery](https://www.wearedevelopers.com/videos/100026-building-10x-organizations-using-modern-productivity-metrics) (from "Building 10x Organizations Using Modern Productivity Metrics") - [Measuring developer experience to eliminate rigid workflow friction](https://www.wearedevelopers.com/videos/100266-ai-won-t-fix-your-engineering-culture) (from "AI Won't Fix Your Engineering Culture") - [Shifting focus from developer productivity to developer experience](https://www.wearedevelopers.com/videos/1698-state-of-devex-2025-navigating-the-ai-revolution-and-developer-experience) (from "State of DevEx 2025: Navigating the AI Revolution and Developer Experience") - [Measuring developer productivity, efficiency metrics, and team happiness](https://www.wearedevelopers.com/videos/100256-can-this-elephant-dance-ibm-bob-and-the-future-of-ai-first-software-development) (from "Can This Elephant Dance? IBM Bob and the Future of AI-First Software Development") - [Measuring actual productivity gains in modern software development](https://www.wearedevelopers.com/videos/1097-collaborative-intelligence-the-human-ai-partnership) (from "Collaborative Intelligence: The Human & AI Partnership") - [Measuring developer workflows through perception and metrics](https://www.wearedevelopers.com/videos/884-forget-developer-platforms-think-developer-productivity) (from "Forget Developer Platforms, Think Developer Productivity!") ## Related Articles - [Now is the time for industrialized software development](https://www.wearedevelopers.com/magazine/601-now-is-the-time-for-industrialized-software-development) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Stop Wasting Time: How to Lead a Stand-Up Meeting & Get Results](https://www.wearedevelopers.com/magazine/414-stop-wasting-time-how-to-lead-a-stand-up-meeting-get-results) - [Get Old, go Slow, Write Code!](https://www.wearedevelopers.com/magazine/81-get-old-go-slow-write-code) ## Related Jobs - [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx** - [Staff Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1470125-staff-software-engineer-database-infrastructure) at **GitHub** - [Principal Software Engineer, Database Infrastructure](https://www.wearedevelopers.com/jobs/ext/1465908-principal-software-engineer-database-infrastructure) at **GitHub** - [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub** - [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub** - [Senior Software Engineer](https://www.wearedevelopers.com/jobs/ext/15942-senior-software-engineer) at **GitHub**