Pluralsight Flow

Pros

We can finally understand what the dev teams are doing, not as a function of closed Jira tickets but as actual work actually completed. GitPrime measures the actual work completed, showing patterns, language analysis (like angular vs react), and visualizes what is going in a less abstract way- because story points can only be so accurate. Basically, we are learning who is deploying, who is working, how they're being so successful, and identifying the weak links. When you have a collaborative team full of selfless introverts, it can be very hard to identify who isn't contributing and even harder to identify who your rockstars are. GitPrime solves all of that, and visualizes the trends and the metrics.

Cons

Price. It can definitely be a little expensive especially when you consider the suite of tools already being used for dev teams (security management, work ticketing, internal wikis, etc.). It does require ongoing management to get the most out of it, it would be more convenient if there were notifications/alerts or something similar.

Pros

GitPrime increases my ability to make confident decisions about performance, and it allows me to do so much more quickly. I no longer have to rely on larger more abstract mechanisms or my gut only, now I can validate or invalidate it with data.

The ability to drive after goals using team based data and/or individual based data allows me to customize how I want to use it across my teams. I also love how it easily and readily gives me coaching opportunities to take to a 1:1 with a team member.

Cons

It's impossible to include all business context into the algorithms GitPrime uses and I'd love a way to have a "journal" of sorts both for individuals and teams that allow documentation of that context over time. Additionally, goals coupled with notifications and updates on goals would be a great improvement.

Pros

GitPrime offers helpful visualizations that add transparency to the development process.

Cons

GitPrime's designed for management, so it's hard to convince actual developers to use it.

Pros

I like their overall approach to quantifying developer productivity. They measure activity, how many commits per day, what areas those commits are in and how long it takes for PRs to be reviewed. This gives granular visibility into each developer and the team as a whole.

Cons

Pricing needed to be addressed. Their pricing out of the gate is from 1 to 25 developers at a fixed price. I have fewer than 25 developers so this put their solution out of reach compared to a competitor that prices per developer. I ended up evaluating both products. GitPrime won on feature and functionality but not on price. The other product was good but incomplete (I wanted Jira integration) but the price was about a third of the cost of GitPrime. At the end of the eval I negotiated on price to something my budget would allow.

Pros

GitPrime peels back the curtain and exposes a wealth of metrics around the productivity and behavior of your engineering team. This allows everything from getting a great 10,000 ft view to diving into a specific team member. We've effectively used the tool to evaluate the impact (or lack of impact) of process/cultural changes, check in on team member performance and evaluate how new team members onboard and ramp up.

Cons

The metrics and charts only provide part of the picture. The software is best used in conjunction with your own intuition. For example, there may be non-alarming explanations for decreases in productivity (e.g. increase of PTO in the summer). Also I wish some of the charts had the ability to graph longer time periods.