What is Resourcing?

Resourcing is a tab specialized for comparing Pull Requests to contributors. Overall, it helps find if your developers are overloaded or not.



Pull Requests Per Contributor each Week

What is Pull Requests per Contributor each Week?

It is a comparative tool that compares the amount of pull requests done each week to the amount of contributors/active developers for that week.

What does Pull Requests Per Contributor each Week do?

Very simply put, PRs per contributor each Week show you the productivity of your team through the week. If the number is too high then it can signify overload. Adversely, if the number is too low it could signify bottlenecks.

Why use Pull Requests per Contributor each Week?

It is one of the primary detectors of overload within the team, and should be watched to monitor team health.

Distribution of Pull Requests Per Contributor

What is Distribution of Pull Requests Per Contributor?

It shows the amount of pull requests each contributor has completed.

What does Distribution of Pull Requests Per Contributor do?

This metric gives an indication of whether developers are overloading themselves or facing blockers. An individual with a number of pull requests higher than average may be at risk of a burnout, while an individual with a lower than average number may be blocked, or is taking on large jobs that could be broken up.

Why use Distribution of Pull Requests Per Contributor?

It is one of the drill-down graphs to find which developer(s) have been overloading themselves.

Opened Pull Requests vs. Total Contributors

What is Opened Pull Requests vs. Total Contributors?

It shows the amount of pull requests each contributor has opened.

What does Opened Pull Requests vs. Total Contributors do?

The graph of Opened Pull Requests vs Total Contributors is another visual representation of whether the team is overloading themselves or facing blockers.

Healthy teams would see planned work increase with contributors count. Not enough contributors relative to planned work could be a sign of taking on too much work and not delivering. Outstanding work withholds resources and increases cognitive load. An accumulating backlog of WIP PRs is detrimental to productivity and morale.

Why use Opened Pull Requests vs. Total Contributors?

Another method to find overloaded developers and maintain a high level of team health.

Did this answer your question?