Batch size
Batch size measures how much work is bundled up in a change. Swarmia offers tools for evaluating pull request batch size by looking at the total number of changes in a single pull request.
Last updated
Was this helpful?
Batch size measures how much work is bundled up in a change. Swarmia offers tools for evaluating pull request batch size by looking at the total number of changes in a single pull request.
Last updated
Was this helpful?
Batch size is calculated by the lines of code changed in a given pull request. This number excludes certain automatically generated files, because generated files can completely render "raw" batch insights ineffective.
In Swarmia, the chart that shows the pull request size vs cycle time shows a set of pull requests in the selected time frame and charts them based on their individual cycle time and the total number of lines of code changed in the pull request. This chart allows you to see correlations between the size of a pull request and its cycle time.
Splitting work in small increments is a great way to improve delivery.
Small pull requests are easier to plan, review, and deploy.
We suggest keeping the pull request size under 500 lines of code and paying attention to work that ends up spanning over 1,000+ lines.
Seeing the distribution of larger batch sizes and higher cycle times can indicate that your team needs to focus on delivering smaller batch sizes. This change can improve not only your cycle time but also your quality.
You can find batch size metrics under Insights → Code → Batch size.
