Concrete Velocity metrics enabled Rodrigo find and advocate for process improvements.
When Rodrigo stumbled upon Velocity, everything clicked. He felt like Pull Requests were the first objective and accurate unit of measurement he has found for software engineering.
Rodrigo could get a sense of how fast his team was moving based on Pull Requests Merged and find patterns in Velocity that correlated with productive teams and sprints. He also looked at metrics that indicated underlying drivers of productivity, such as the number of reviews, the time to review, and revert count.
One of Rodrigo’s discoveries was that when the team pushed smaller PRs, they tended to ship features more frequently. So he and the other leaders set a new goal: no more PRs larger than 400 lines of code. “We noticed a correlation between the size of a pull request and cycle time. This led to an organization-wide emphasis on limiting the size of pull requests.”
Team leaders look at Velocity together every two weeks to see where the team is doing well and where there are further opportunities for improvement. Once goals are set, individual engineers get daily emails summarizing any pull requests that are outside of the targets set. This gives everyone, from individual contributors to team leads to engineering managers an opportunity to improve the team.
Within three months, Resultados saw a 26% increase in pull requests merged across the organization. Rodrigo discovered a way to scale the efficiency of their growing engineering organization.