The trails-counter team pairs only when there is extra time, and a review queue piles up at the end of every iteration. What should the SM/TC coach?
Select an answer to reveal the explanation.
Short Explanation
Pairing only when leftover minutes appear is like checking trail maps after hikers are already lost. Two sets of eyes while the counter story is moving beats a review pile at the gate. Make pairing the default so quality rides with the work.
Full Explanation
Pairing and peer review are Built-in Quality practices that move learning left and reduce handoffs into a late review column. When the trails-counter team pairs only if spare time remains, knowledge stays siloed and a review bottleneck forms at iteration end, stretching flow time. Treating pairing as overtime, a utilization waste, or a separate inspection desk after code-complete keeps that interrupt. The SM/TC should coach pairing as normal work so review is continuous and flow improves.