For SaaS companies to remain competitive, it’s important that they’re able to ship features and code at a fast pace—which means they need to ensure their employees are able to keep up with the speed required.

A good way of measuring the team’s overall velocity is to calculate the time between when a pull request (PR) is created and when it is merged—if that duration is longer than expected, it could point to an issue somewhere within their process that requires attention to resolve.

For example, the slowed speed could be due to new employees that need a little extra training, or an understaffed team that results in PRs being left unreviewed longer than they should be.

With this Recipe, you’ll be able to pull data from GitHub to view how long it takes between a PR being created and when it is merged—and group that data by employee, team and more. That way, it’s easy to identify any trouble areas that require addressing.

Want to add device performance data to your report? As with all our report Recipes, you can customize this template with additional data, filters, grouping and more to help you answer your specific questions.