“Never had a huge Pull Request that didn't look good to me” is, sadly, a reality of so many teams in our industry.

Fortunately, some other teams recognized the value of applying the Small Batches idea from Lean to the PRs.

But, what if I told you that teams doing small PRs with async code reviews, actually have way lower throughput than teams doing big PRs?

I got this surprising systemic insight by analyzing tens of thousands of PRs across a bunch of repositories.

On the bigger PRs side of the spectrum, we tend to lose quality, while on the smaller PRs end of the spectrum we lose throughput. We're forced to make a trade-off between speed and quality.

But! There's a parallel universe of ways of working where you get to have your cake and eat it too. Where you can have both throughput and quality. Universe called co-creation patterns (Pair and Mob programming).

Join me on a journey where I'll show you the data invalidating the assumption that two or more people sitting at the same computer will hurt the team's throughput, and why the opposite is actually the case.