Git Velocity is a set of metrics and data around Git activity that can help you and your teammates work more effectively with Git and with each other. The purpose of collecting and using these metrics is to ship quality code more frequently with fewer bugs. These foundational elements are findings from the DevOps Research and Assessment (DORA) report by Google. 

In this session, we’ll cover 4 key Git velocity metrics:

• Throughput: How often code is successfully pushed to the production environment.
• Lead Time for Change (Cycle Time): The amount of time it takes a commit to get into production.
• Change Failure Rate: The percentage of deployments causing a failure in production.
• Mean Time to Recover: How long it takes to recover from a failure in production.

At GitKraken, we are exploring ways we can provide these types of metrics to development teams, and also use them ourselves. We are in the early stages of designing and building a Git Velocity service. Join this session to be the first to see our initial designs, ideas, and functionality.

Target Audience:
All (General information for everyone)

Theme:
GitKraken Session

Thursday, September 23
1:45 – 2:00pm PDT