Code Climate Velocity Reviews & Product Details

As a DevOps Manager I found the the system provides valuable insight into the activity around a code repository. The views are built in and easy to use. Multiple repositories that make up a deployed application can be linked together and provide a complete picture of activity. The information provided also reduce the amount of information we would have to scrape out of github and the custom endpoints to collect/store the data.

I have not viewed other competetors but its not entirely out of the question. Review collected by and hosted on G2.com.

The API documentation is incomplete and lacking proper descriptions. Support is slow to respond and certainly does not understand what you are asking.

Would like to see it more DevOps friendly: easier to integrate new repositories, documentation that google can find (kept sending us to competetors), and API that is properly defined and does not return you a value if you hit a metric that does not belong to a filter. Review collected by and hosted on G2.com.

It is a nice tool to summarise the data from multiple sources. When you are in doubts of someone's performance, it makes your life simpler in reviewing his/her progress over the recent period of time. Review collected by and hosted on G2.com.

In general, I thin kthat the metrics (no matter what they are) are hardly comparable across teams. Teams usually work in not exactly same schema and therefore differences in their way of working seems to be accceptable. If these metrics are being really used by management, it just leads to changing people's behavior to satrisfy metrics, not the good purpose Review collected by and hosted on G2.com.

When development process matches what Code Climate is designed for, the tool works very well. It provides a great picture of performance and is good for tracking improvements within a team that follows a consistend process. Code Climate is a good tool to support retrospectives and continuous improvement efforts. The integration between different tools (JIRA and Github in my case) allows me to see in a single place all the important metrics for my team. Review collected by and hosted on G2.com.

Any inconsistency in the process, such as a single PR that deviated from standard process, can really skew results. There is limited ability to fix data issues once process mistakes were made. This means all results that seem significant require substantial manual review to confirm their significance. There are other options, such as automation to enforce process practices, but the overhead of building automatic enforcement of process, also comes at a significant cost. These factors combine to reduce the effective ROI from using Code Climate. Review collected by and hosted on G2.com.

As orgs scale, it can be extremely hard for executives and leadership to understand which teams are impacted or blocked. Large orgs make it impossible and highly unproductive to spend much time in code reviews, PR reviews or in standups, nor is it a smart use of time. CodeClimate provides an easy-to-digest overview of team health, allowing you to identify which teams may be blocked and then focus on specific areas to unblock them. CodeClimate has been the single most valuable tool in my toolbelt through multiple companies and roles, and I would recommend it to any leader at an organization of any size. Review collected by and hosted on G2.com.

User management and team assignments/updates can be challenging if people often move around to different teams. Would love to see a tighter integration with some of the other tools that Product/Engineering teams use on a regular basis to provide a more complete picture of team health and productivity. Review collected by and hosted on G2.com.

Velocity is incredibly easy to use and drill down into Engineering productivity metrics. It connects with every tool we use, including Github and Jira and reveals all the DORA metrics we want to see, activity, throughput, etc. Review collected by and hosted on G2.com.

Tracking of key organizational events, like process or personnel changes, can be easier - I'd love to be able to see when these events occured alongside the metrics and charts to see possible impacts. I'd also like to create my own dashboards, and see more robust aggregation / breakdowns of metrics. Review collected by and hosted on G2.com.

It's a really powerful development insights tool. The reality is that the limit is what you decide to do with the data and how to build on top of it, cross-referencing activity Velocity crunches from GitHub with what's available in Jira can lead to some rather interesting reports. Although there's plenty of reports available there's a few favorites that we rely on for our engineering KPIs and the Analytics section is the ultimate resource to fall back to. Review collected by and hosted on G2.com.

There's a few minor usability concerns (that I think the team is working on at the moment):

+ Certain kinds of GitHub activity can't be excluded (like Reviews)

+ Foundations (which is perhaps the rockstar report for Developer360 and Team360) cannot process date ranges and relies on certain presets (1 month, 3 months, 6 months). Review collected by and hosted on G2.com.

I love that I have the ability to view my team's, as well as IC's, performance at a granular level. Understanding developer performance is always such a challenging task. Review collected by and hosted on G2.com.

Some of the metrics within Code Climate are a little vague. Metrics like "Impact" sound like it would provide tremendous value however, a deeper understanding of what actually goes into that metric would be much more helpful to assess its true value. Review collected by and hosted on G2.com.

Code Climate provide visibility into the challenges experienced within teams before they start to significantly impact team satisfaction and performance. The ability to compare team members against company benchmarks provides valuable insights to the individual allowing them to optimise their contribution Review collected by and hosted on G2.com.

It can be hard to related trends in metrics to factors that occur outside of Code Climate. For example it would be ideal to be able to make notes on an individual users activity view to record that they were on leave, attending training etc to allow for visibility for other users. It would also be beneficial to exclude individual days from daily/weekly average metrics to ensure they are not skewed but factors like PTO. Review collected by and hosted on G2.com.

The tool provides great insights into the company team's performance, such as Lead and Cycle time. The integration with the source of truth of teams - GitHub is easy to set up and manage.

The UI is intuitive and there is no need to read documentation to find things. Review collected by and hosted on G2.com.

The API could be improved. Recently I integrated with Code Climate Velocity and used the Team API to fetch all of the teams per account. The API call returned only 90% of the teams. Review collected by and hosted on G2.com.

I'll be honest, my company has had this software running for a few months now and I receive daily emails. I have not yet figured out how to make use of the software for anything. I glance over the pretty graphs and that's about it. Maybe the software is too powerful and I have simpler needs? Maybe I need to be spoon fed more? Review collected by and hosted on G2.com.

For me personaly it's not intuitive how I can use the data. I'm sure there is a lot of science behind this tool but I'm not using it; to me this is a problem. Why install this software if most of the users can't figure out how to get any use out of it. Review collected by and hosted on G2.com.