How to manage pull request review and approvals

In our team we have a recurrent problem that we are not able to solve. As long as the team grows, we tend to accumulated PRs at the end of the sprint / release and these become a bottleneck to advance in our daily tasks, and at the same time, at the end of the sprint we have to let our work to review PRs. Our goal is to get to the end of the sprint / release with the most of PRs reviewed, but the team does not review PRs during the sprint (due their daily tasks, their work and issues) I post this problem because I would like to know the strategies other teams follows in order to aboard the Pull request management Our team is composed by 7 developers and the PRs needs at least 2 approvals to be merged Thanks

Jun 11, 2025 - 08:00

In our team we have a recurrent problem that we are not able to solve. As long as the team grows, we tend to accumulated PRs at the end of the sprint / release and these become a bottleneck to advance in our daily tasks, and at the same time, at the end of the sprint we have to let our work to review PRs.

Our goal is to get to the end of the sprint / release with the most of PRs reviewed, but the team does not review PRs during the sprint (due their daily tasks, their work and issues)

I post this problem because I would like to know the strategies other teams follows in order to aboard the Pull request management

Our team is composed by 7 developers and the PRs needs at least 2 approvals to be merged

Thanks