On the building-permits team, pairing is framed as “we go half as fast.” How should the Scrum Master / Team Coach reframe the quality debate?
Select an answer to reveal the explanation.
Short Explanation
“Pairing makes us half as fast” counts keystrokes and ignores the bounce-back from failed inspections. Permits that come back are slower, not faster. Measure the whole trip, including rework, not how quickly someone types alone.
Full Explanation
Local speed without pairing often hides defects that lengthen permit flow time. The Scrum Master / Team Coach reframes the debate around end-to-end flow including quality and rework, which is the relevant system measure. Dropping pairing to “go faster,” mandating pairing by policy, or scoring individual velocity all keep the local-speed frame. Built-in quality improves flow; the reframe makes that visible in the conflict.