An atomic change is a narrowly focused, self-contained unit of work. In practice, it produces a smaller pull request with fewer files, fewer lines, and less cognitive overhead for reviewers. section 9.2.2
Making review feasible
When a team says it has no time for code reviews, split planned, designed, and developed work into smaller changes. Treat the resulting review as required work rather than leaving it as an optional safeguard. section 9.2.2
Teams can protect time for reviewing atomic changes by:
- Adding estimated review time to the story. section 9.2.2
- Listing code review as its own task. section 9.2.2
- Carving out review hours or reducing planned work. section 9.2.2
