Dev Roundup: What GitPrime is like from a developer’s perspective
Using data to inform decisions and increase performance is a trend that’s been gaining adoption from hundreds of software teams around the globe.
Forward-thinking engineering leaders now have the visibility to understand what makes a team productive and how to continue making improvements.
So, what is it like to begin using metrics… as an engineer?
We spoke with several developers to get their take on what it’s like to be part of a team using GitPrime, and their experience using data as part of the development process. Here’s what we learned:
Bring data to the table
Help your engineers own and understand their data, and you lay a foundation upon which your team can improve — and communicate — with confidence.
James Perlman, with Lottery.com
“Before using GitPrime, our visibility into our work was somewhat cloudy, and each sprint was more of a blur. Since we’ve incorporated it into our sprint retro, we’re able to reflect on what we accomplished each week, which helps us track what worked and what didn’t. It’s also a good memory exercise which has proven beneficial when debugging and reducing duplicate work.”
“Using metrics in our team has helped us keep track of what the entire team is working on. Sometimes this is covered in our standups, but seeing these reports helps us stay in touch with what other people are doing in different areas of the codebase. “
Madeline Mayer, with BrightLink
“Rather than saying “I think this will make it better,” I appreciate being able to try different approaches and actually track my progress. Also, having data to back my case helps me feel confident when I want to make suggestions to my team. It’s more impactful.”
“Having data to back my case helps me feel confident when I want to make suggestions to my team. It’s more impactful.”
Aaron Renner: @bayfieldcoder
“GitPrime gives the management team insight into how each developer is doing, which is key because sometimes managers can get out of touch. I felt like they were thinking I wasn’t doing much, when I was doing a lot of code cleanup and refactoring. When they implemented GitPrime, it turned out I was one of the most productive developers. It’s nice to have your numbers show what’s really going on.”
Level-up your team
When data-driven engineering is part of your culture, you enable developers to own their own continuous improvement.
“Shortly after GitPrime was introduced in our team, engineering established a goal to reduce waste. Everyone was tasked to find a way they could reduce waste. I decided to track my tt100 Productive and Churn.”
“I noticed that when I worked on tickets that weren’t well defined—diving right into tasks without planning it out beforehand—my tt100 would be much slower than average. It seems backwards, but I focused on slowing down my work and making sure I had a plan before I started coding. My code improved, and my efficiency increased—and my teammates and managers noticed.”
Gavan Woolery, with Lawn Love
“After getting in the habit of committing more frequently, and more importantly, consistently pumping out work, my performance has increased dramatically. I feel this has generally reflected my ability to output code effectively – not just in raw lines, but actually finishing discrete tasks. I used to fall into the trap of equating working longer hours with outputting more work, but now I am leaving work earlier in the day and accomplishing more in a shorter amount of time.”
“I used to fall into the trap of equating working longer hours with outputting more work, but now I am leaving work earlier in the day and accomplishing more in a shorter amount of time.”
Increase collaboration and communication
When you decide to begin using metrics to track your performance, consider getting everyone involved. Data-driven reporting facilitates better communication, increased collaboration, and a greater awareness for what’s working and what can be improved.
“We use the “Daily Update” daily (as intended!) but we also do monthly code reviews to see how our performance stacked up against the month prior. We use almost all of the reports in GitPrime to try and locate areas where we can improve our performance. We also match up the performance indicators with actual work accomplished during that period, in terms of shipping features or fixing bugs, and try to locate the causes of any extreme outliers in the charts.”
“We didn’t realize how many pull requests were just hanging around until we started using GitPrime. We were like, “Oh, man. There are so many open pull requests that never got closed out.” Some of those were because BitBucket misbehaved and didn’t close it when we thought it did. We had a team meeting where we made the decision to just sit down and spend time closing them out.”
“Now we have weekly meetings where we use GitPrime to reflect on our work, and collaborate on what’s working and find areas where we can improve. We’ll analyze our tickets and notice things like a lower efficiency rate, and be able to recall that the project’s requirements weren’t well defined, or that the code was especially complex. We can collaborate on ways to improve, experiment with new processes, and track our progress.”
“We can collaborate on ways to improve, experiment with new processes, and track our progress.”
Get Engineering Impact: the weekly newsletter for managers of software teams
Keep current with trends in engineering leadership, productivity, culture, and scaling development teams.