What does a widening CFD Code Review band indicate?

WHAT THIS TESTS: This question tests whether you can read a Cumulative Flow Diagram as a diagnostic instrument rather than a vanity metric. Specifically it checks your grasp of work-in-progress accumulation, bottleneck identification, and the relationship between queue growth and cycle time. Interviewers want to see that you connect the visual shape of a band to underlying process physics and that you prescribe systems-level fixes before resorting to headcount.

A GOOD ANSWER COVERS: A strong answer states immediately that a widening band means the amount of work residing in Code Review is increasing over time while the departure rate from that stage remains flat or lower than the arrival rate. You should name this as a bottleneck and note that by Little's Law cycle time will rise predictably unless addressed. The response should then sequence concrete interventions in order of cost and friction: first enforce or lower a WIP limit on the Code Review column to throttle new arrivals; second swarm the queue by having developers who are blocked do reviews rather than start new work; third inspect entry criteria and batch size so reviews are smaller and more uniform; fourth examine policy constraints like mandatory reviewer count or timezone handoffs; and only after those changes consider adding reviewers. Mentioning that you would validate the fix by watching the band flatten and monitoring average age of items in review shows data-driven closure.

COMMON WRONG ANSWERS: The most common red flag is interpreting the widening band as evidence of higher throughput or more work being completed. Another frequent mistake is jumping straight to hiring more senior engineers or reviewers without first optimizing the existing system. Some candidates also confuse a widening band with scope creep or total project growth rather than a localized queue. Suggesting that developers simply work faster or skip reviews is a culture and quality red flag. Finally blaming individuals rather than the system signals a lack of systems thinking.

LIKELY FOLLOW-UPS: An interviewer may ask how you would distinguish a temporary spike from a systemic trend. They might probe what other CFD patterns you watch for such as flat lines indicating stalled work or disappearing bands showing neglected states. You could be asked how WIP limits interact with service level expectations or how you would communicate the bottleneck to stakeholders without eroding trust in the team.

ONE CONCRETE EXAMPLE: Suppose the Code Review band grows from three items to fifteen over four weeks while the Done line rises linearly. You check the board and find no WIP limit on the review column and a team norm that only senior staff may approve. You propose a two-week experiment: set a WIP limit of five reviews in progress, require any developer with idle time to pick up a review, and split stories so no review exceeds four hundred lines of changed code. You predict the band will stabilize and the average age of items in review will drop from six days to under two days within three sprints.