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.

1. All kinds of features related to productivity in code development such as stats on PR discussion cycles, commit frequency and lines of code

2. Being able to organize members by team and show stats by team is great because different teams work differently and work content also decides the metrics

3. All engineers have access to the stats so that there is transparency around what's used to evaluate productivity Review collected by and hosted on G2.com.

Only code repos are used as the source of stats and there is no way to track additional work around code maintenance and other things that might be useful to visualize someone's efforts put in these areas. Review collected by and hosted on G2.com.

The metrics are thorough and easy to set up and analyze. Provides great insight into our teams' performance so we can watch trends and try to equate changes to what may be going on to cause throughput or code quality changes. Review collected by and hosted on G2.com.

We have had a few issues where various integrations break, causing gaps in the metrics. Support is usually quick to help us to resolve these issues, but it is disruptive to our reporting processes when it happens. Review collected by and hosted on G2.com.

Particular metrics I leverage a lot to form the story for engineers is coding days, code reviews, and PR throughput. Though it does not give the full story, it comprehensively provides the snapshot of coding activity for individuals and teams.

The visualization of coding activity throughout a calendar view is very helpful to diagnose periods of time I can surmise an individual is motivated vs not motivated with their work. Review collected by and hosted on G2.com.

Some metrics are not as useful because the realities of the job can heavily skew the values and thus I do not pay attention to them at all. Review collected by and hosted on G2.com.

Analytics. Being able to build out the metrics we're focused on with the ability to save as reusable reports. Compare feature. I love this. To be able to evaulate across teams/users to identify outliers, top performers, or areas are concern are extraamly valuable. Review collected by and hosted on G2.com.

Targets but I bleive that is a result of how we're not fully using that feature. Review collected by and hosted on G2.com.

Code climate has allowed me to better visualize and track my team's analytics from GitHub. This has allowed us to highlight areas in need of improvement and follow up on those goals. I have also found the notifications very helpful in receiving an overview of my team and getting notifications of potential risks on our open pull requests. Review collected by and hosted on G2.com.

Code climate makes some assumptions about how your team utilizes GitHub and the pull request process. Our team doesn't always follow a traditional routine, which can throw off some data. Review collected by and hosted on G2.com.

I came upon the Velocity services by chance, more or less. But got immediately attracted. It promised a comprehensive portfolio of metrics capturing vital aspects of the SDLC and their evolution in time. It is easy to follow up on trends forecasted. And all the insights gained are then very accurately factored by the custom teams the user defines.

General team productivity, code reviews, PR resolutions, pull requests monitoring major team KPIs can be observed in perspective. In that respect, Velocity is the perfect tool to support decision-making regarding interpreting speed and agility. Review collected by and hosted on G2.com.

I haven't thought about any significant drawbacks. Having seamlessly integrated the findings into our organization's CI/CD pipelines, the overall status of the development has always been visible in our products and perfectly signals when an issue is to be addressed. Review collected by and hosted on G2.com.

I can see what impacts my team's delivery capacity (whether it's time for review or if they're taking too long to develop, for example). Also, I can see how much review coverage Pull Requests are getting, the length of the review cycle, and other critical points.

It is also possible to analyze the number of days a developer has been writing code effectively (coding days). All this, in addition to the already standard metrics (Troughput, Defect Rate, Rework and others) Review collected by and hosted on G2.com.

Despite having several things that can be analyzed on the platform, this makes the interface a little confusing and not very intuitive. There are many views in many different screens, which makes it difficult to get value quickly (you need some time to get used to the platform) Review collected by and hosted on G2.com.

- Velocity leverages our GitHub data, which is a better source of truth than workflow/project mgmt tool data (i.e., JIRA). It solves for the "delivering quality code is the goal, let's measure that" philosophy.

- Out-of-the-box reporting is good, there are sane defaults and the setup process was unbelievably simple. We picked up historical data right away, which can be used to gauge progress quickly as we implement process improvements.

- Customizable reporting, including saving reports.

- All the interactions with the CC team have been good. Pre-sales and now customer success has been super helpful in finding the best ways to extract value. Review collected by and hosted on G2.com.

A feature request would be for more reporting and visibility around work in progress (WIP) and also the ability to compare some metrics against industry benchmarks or other companies. Review collected by and hosted on G2.com.

Velocity is a handy analytical tool for software engineering leaders (managers, CTOs, and VPs of Engineering).

It gives you a lot of data and information to understand better your team metrics related to throughput, quality, waste, etc.

You can create visions for individuals, squads, tribes or your entire team. The teams (and sub-teams) configuration is very flexible. And you can compare the metrics with worldwide benchmarks.

As a Director of Engineering who manages over 100+ engineers, I recommend Code Climate Velocity. Review collected by and hosted on G2.com.

In my opinion, there is nothing to dislike about Code Climate Velocity. Review collected by and hosted on G2.com.

I use code climate every sprint, honestly I can track my own performance, its great for my own reviews when it comes to being able to track what I've done and how I'm compared against my prior attempts. At the end of a sprint I can use it to track any work projects that are still open and its health statistics (although harsh) allow me to see what is useful to my colleagues. Review collected by and hosted on G2.com.

The global settings in the custom alerts can be infuriating and more easily accessible granularity would be good in order to see an improvement. I know that a lot of these are down to the company but its the intuitive element that counts. Review collected by and hosted on G2.com.

Velocity is a great tool that clearly and easily presents the key metrics that have let us retool our development workflow. The key indicators that it tracks and reports on allowed us to make changes to our development process and immediately see the impacts on our productivity. We continue to iterate with new changes and are able to quickly see which are effective and which are not. We are clearly a better development team with the help of Velocity. Review collected by and hosted on G2.com.

Velocity captures a lot of metrics and reports on them in numerous ways. It can be overwhelming when you first get started if this is your first exposure to that volume of information. However, with our CSM, and the online help available, we've been able to generate the reports we need and follow the metrics that most effect our efficiency. Review collected by and hosted on G2.com.

The product is easy to understand and to use, good velocity delivering new features, and also the support is very fast answering questions. Review collected by and hosted on G2.com.

Code Climate Velocity focuses on tracking the activity of individual developers. The downside to having different views for different user levels is that it can create mistrust in the organization and make developers feel like they're being watched. Review collected by and hosted on G2.com.

There is a ton of metrics to view. I can look at pull requests, commits, perform comparisions and reports based on those metrics. I like the ability to create teams and group developers together. Review collected by and hosted on G2.com.

Some of the metrics are missing. I'd like to more easily perform a year in review. There is a metric for year todate and last 12 months. I'd like to see a range of last year, or by year, etc. This will allow me to change reporting around easily. Review collected by and hosted on G2.com.

Data data data. Great data and graphs and views with team and dev 360. Analytics is grate to view data side by side. Then if you need more there is reports builder. Review collected by and hosted on G2.com.

Lack luster Pull Request timeline view. Reports builder is hard to use and feels like separate product. Most advanced settings either are hard to understand or don't work as expected. Specicially targets and permissions, and roles for teams. Just because a manager is on one team doesn't mean he is a manager of another team he is on. Especially when using teams as "SME" teams or "Cohorts". Review collected by and hosted on G2.com.

I like having the ability to create reports for different teams in my org pretty easily given the metrics available. Review collected by and hosted on G2.com.

I think the model for permissions and access is a little tricky. Maybe it's just how my org is set up but I think not everyone has access and it seems there should be more "view" only seats so teams can access their own reports. Review collected by and hosted on G2.com.