Velocity helped Boaz measure and improve the rate of innovation.
Boaz started using Velocity, because the tool measures engineering speed based on a concrete metrics. Boaz tells us, “If your engineering team has a standard around pushing small Pull Requests, then Velocity’s metrics become objective measures of how much your team is getting done.”
Boaz looked at Pull Requests Merged per team and realized that his R&D team was one of the fastest in the organization. He tells us, “The visibility is amazing. Velocity showed how well we were doing but showed us there are still lots more opportunities to be more efficient.”
Boaz scrapped his existing KPIs around deviation from planning and started setting benchmarks according to Velocity metrics. Rather than looking at planning vs. execution, tasks per day and uptime, he started tracking Pull Request Throughput, Pull Request Size, Reverts and Rework (how often a contributor edits recently merged code.)
Boaz found that sharing these metrics with the team incentivized really positive work habits, from the individual to the team, to the organization. As a result, Boaz said “my team developed a winning attitude and were eager to find ways to get even faster.” Within the first year of using Velocity, they boosted their Pull Request Throughput 95%.