Published Sep 3, 2019

SE-Radio Episode 317: Travis Kimmel on Measuring Software Engineering Productivity

Travis Kimmel delves into enhancing software engineering productivity by leveraging metrics and empowering leaders with data-driven strategies, addressing the challenges of remote team management and the intricacies of handling legacy code to align engineering efforts with business goals.
Episode Highlights
Software Engineering Radio - the podcast for professional software developers logo

Popular Clips

Episode Highlights

  • Productivity

    Enhancing productivity in engineering teams involves adopting data-driven strategies that focus on specific metrics. emphasizes the importance of granular delivery, where engineers check in smaller, more frequent commits to avoid operational overhead and merge conflicts 1. This approach allows for better communication and integration among team members, fostering a more efficient workflow. He advises starting small with data initiatives, targeting specific pain points, and iterating on improvements 2. notes, "It's really about breaking this stuff up into accessible chunks and making the problem whatever thing you're working on, something that is immediately addressable and tractable."

       

    Remote Teams

    Managing productivity in remote engineering teams presents unique challenges, but data-driven metrics can offer solutions. highlights the difficulty of assessing remote team progress without proper tools, noting that metrics can help bridge this gap by providing clear insights into team activities 3. He advocates for engineering-led discussions about data to ensure that metrics serve the team's needs rather than external agendas 4. "Remote teams benefit a lot from metrics-driven environments because you can answer for deliverables," explains, emphasizing the value of clear deliverables and defined roles in remote settings 5.

       

    Legacy Code

    Addressing legacy code is crucial for maintaining team efficiency and software quality. discusses the importance of identifying when refactoring becomes excessive, suggesting that if over half of a team's focus is on legacy code, it may be time for a significant architectural overhaul 6. He stresses the need for team leads to manage these efforts effectively, ensuring that engineers focus on impactful tasks rather than getting bogged down by technical debt 7. "Start small," advises, "focus very narrow on something to improve first," to prevent teams from becoming overwhelmed by multiple priorities 8.