Code review time is the duration needed to examine and evaluate a proposed change. Smaller, atomic pull requests reduce it by limiting files, lines, and cognitive overhead. section 9.2.2
Teams can make review time visible and protect it by:
- Adding estimated review time to a story or listing review as its own task. section 9.2.2
- Reserving specific review days or hours, or reducing planned sprint work to create capacity. section 9.2.2
- Pairing review-time metrics with contextual discussion instead of using them to justify cutting corners. section 9.3
Making review capacity explicit
A team plans review time alongside feature work, keeps changes small, and reserves dedicated hours when normal delivery pressure would otherwise displace reviews. section 9.2.2
