Software Engineering Productivity | Walter de Bruijn | Beyond Coding Podcast #174

Topics covered
Popular Clips
Questions from this episode
- Asked by 256 people
- Asked by 34 people
- Asked by 31 people
- Asked by 3 people
- Asked by 1 person
- Asked by 1 person
Episode Highlights
Frameworks
discusses the importance of choosing the right framework for measuring software engineering productivity. He highlights the Dora metrics as a starting point for gaining engineering insights, focusing on code production and deployment efficiency. The Space framework, on the other hand, broadens the scope by including aspects like satisfaction and productization, making it more complex but comprehensive 1. Walter advises involving teams in the process to ensure the data is used for continuous improvement rather than tracking 2.
If you really want to dive deep, there's excellent material in how to get started with Dora metrics.
---
shares his experience of merging teams to streamline productivity measurement, emphasizing the need for both qualitative and quantitative data 2.
Challenges
Walter addresses the challenges in measuring productivity, particularly the complexity of data management. He explains that while tools exist to extract data from repositories and ticketing systems, inconsistencies and complexities can arise, especially when teams use different processes 3. Patrick notes the importance of understanding what to measure and ensuring that data is used for improvement rather than as a tracking tool 4.
You have the mandate and leadership is willing to commit in it as well.
---
Walter emphasizes the need for early involvement of teams in deciding what metrics to track, to avoid the perception of being monitored and to foster genuine improvement 4.
Well-being
The relationship between productivity metrics and engineer well-being is complex. Walter argues that while productivity should enhance happiness, using metrics as performance targets can lead to gaming the system and erode trust 5. He stresses the importance of focusing on team performance and continuous improvement rather than individual tracking, which can be misleading 6.
If you start only optimizing on I want to go faster and the quality shouldn't be influenced there, you will pay the price eventually.
---
Patrick reflects on the potential for burnout in the tech industry, questioning whether increased productivity necessarily leads to greater happiness 5.
Related Episodes


Building Products for Growth at VEED.IO | Willem Evers | Beyond Coding Podcast #167
Answers 383 questions

High Quality Software Development | Eugene Fidelin | Beyond Coding Podcast #165
Answers 383 questions

Software Development and Sustainability | Brendan Kamp | Beyond Coding Podcast #160
Answers 383 questions

How to Innovate with Software | Carlos Kelkboom | Beyond Coding Podcast #118
Answers 383 questions

Developing People | Ester Le Roux | Beyond Coding Podcast #164
Answers 383 questions

Code Automation Software | Gareth Baars | Beyond Coding Podcast #8
Answers 383 questions

Effective Software Teams | Daniel Terhorst-North | Beyond Coding Podcast #59
Answers 383 questions

How to Build a Product Company | Andreas Prins | Beyond Coding Podcast #104
Answers 383 questions

Quality in Software Development | Dennis Doomen | Beyond Coding Podcast #13
Answers 383 questions













