During spring planning we are planning story based upon our teams velocity over time, to avoid over committing we are also noticing that Merge Request take a significant amount of time during a sprint to go through the initial review, and then the final reviews or senior reviews.
The team was to commit up front during planning for each story who will be the initial team member assigned to commit to the initial merge request.
In this way during Sprint planning we can see the story points we are committing to, as well as a team we can review who is assigned to complete the initial merge request.
This is a team where we are also using the 1st review as a way to pass on knowledge to those who want to learn the frontend or backend, or learn the code review practice at the organization.
There is a custom field that we use, but as you imagine that requires being up a query to see who we have assigned reviewers to during the sprint planning view.
Has anyone experimented with something like this to ensure that the team does not overcommit with Story points and the time that we spend on code reviews with a team that is growing in knowledge on the platform.
