Engineering productivity, metrics, & morale

-

You will find below my talk (sponsored by the non-profit https://big-on.dev/ in Singapore) on engineering productivity, metrics, and morale.  The questions were awesome. 😎

It's all about psychological safety for the team for the best combination of team morale and team effectiveness.

Summary

Development metrics

  • Team productivity: Per department and per team merge request (AKA pull request) rate, defined as the number of requests merged divided by the number of employees on that team
  • Productivity of the review process: Open merge request review time
  • Quality: Past due issues by severity and type (customer-facing, security, infrastructure)
  • Web application performance: LCP (largest contentful paint) 
  • Backend application health: Error budgets (error rates and performance analysis per service/endpoint)
  • Investment: Issue count by weight by type (feature, bug, maintenance, other)

Team Morale

  • Use a combination of sync (meeting) and async (in writing) discussions, with async being the priority.
  • Turning on video during meetings is highly encouraged.
  • Recording meetings when possible
  • Always explain the "why" and not just the "what"
  • Release retrospectives (what went well, what didn't, what actions to take)
  • Quarterly social activities
  • Social slack channels
  • Skip level meetings and AMA (ask me anything) sessions
  • NPS (net promoter score) for employees

Remote and results

  • Measure results, not hours
  • Hire where the best people are (vs in central locations)
  • Written processes 
  • Written knowledge
  • Transparent sharing to increase collaboration
  • Anyone can contribute

Video

Productivity metrics morale video

Slides

Productivity metrics morale slides

 

Comments

Post a Comment

Popular posts from this blog

Unpacking GitLab's Strategies for Building High-Performant Distributed Teams With Wayne Haber

-
Image
The video is a part of Adeva Fireside Chats, it is a thought-provoking discussion with Wayne Haber, Director of Engineering at GitLab.  Explore the dynamics of remote excellence with Wayne Haber, Director of Engineering at GitLab. This discussion will cut straight to the core of GitLab's approach to managing distributed teams, the pragmatic benefits of asynchronous work, and the practicalities of using GitLab's own tools to oversee the development lifecycle. Tailored for CTOs and tech leaders, this conversation delivers direct insights into refining remote operations, enhancing team performance, and leveraging Gitlab's firsthand experiences to navigate the complexities of a distributed workforce.
Read more

Podcast: Showing Vulnerability as a Leader | A Conversation With Wayne Haber | Tech Done Different Podcast

-
Image
Episode Description Our guest Wayne Haber, the Director of Engineering at GitLab. Talks about everything from where attackers get their motivation to why showing your team your vulnerabilities is healthy for everyone. You’ll Learn How to make #remotework most effective for you and your team Why we need to change our expectations on instant response for ourselves and our team members How a large company like GitLab works to keep attackers from using their services in malicious ways Why  servant leadership is so important inside and outside of business Learn from the people you lead everyday When you are vulnerable as a leader it will show your team they can do the same Why when you want to make a change in your company it’s so important to bring the data to support your position Podcast Tech Done Different
Read more