Velocity: automatic DORA metrics for product teams
Deployment frequency, lead time, change failure rate and time to restore. This is how Velocity, the DevOps module of DevPulse, computes the four DORA metrics without spreadsheets.
Product & communication
DORA metrics, defined by the DevOps Research and Assessment team and popularised by the State of DevOps report, are the de facto standard for measuring software delivery performance. The problem is that computing them by hand is tedious and unreliable. Velocity, the operations and DevOps module of Simvix DevPulse, obtains them automatically.
The four metrics
Deployment frequency: how often code reaches production.
Lead time for changes: how long a commit takes to reach production.
Change failure rate: the share of deployments that cause incidents.
Time to restore service: how long it takes to recover after a failure.
Where the data comes from
Velocity connects to code repositories, continuous integration systems and incident management tools. From those three sources it rebuilds the full cycle of each change, from the first commit to deployment and, if any, to the incident and its resolution.
What to do with them
The metrics are not meant to compare people but to reveal system bottlenecks: review queues, slow environments, manual deployments. Velocity shows trends per team and service and relates them to process changes.
Integrated with the rest of DevPulse
Because Velocity is part of the suite, delivery data lives next to projects, incidents and people. A manager can see, for example, how lead time changed after reorganising a team or automating a pipeline.
Start in minutes
Connecting a repository and a CI system takes minutes. If you want to see your DORA metrics in DevPulse, request a demo.