I'm always objective focused with my team... 1. we breakdown issues/bugs into 2 - 4 hour increments where we write test(s) to replicate. Then share with team.

I'm always objective focused with my team... 1. we breakdown issues/bugs into 2 - 4 hour increments where we write test(s) to replicate. Then share with team. Hopefully there can be a fix in that time, else create a new issue. 2. we breakdown new tasks into 2 - 4 hour increments with a new function(ality) + necessary tests Then we spend ~1 hour a day doing code reviews. Some days I can get through multiple issues, some days it's just 1. In either case, we can assume 5 - 8 tasks / issues a week are completed. How everyone does it is up to them; so that's how you decide how much work you need to do. Unfortunately, estimating can be poor for these tasks, but that's why we time box it and require a team notification for any issues (plus tests). It works relatively well, and everyone checks for open PRs or code reviews between each task -- so blockers don't occur. I recommend trying something like that.