Election-night reporting throughput on a civic results team is high one week and drops to zero the next. Leadership wants to treat the spike as the team's true speed. What should the Scrum Master/Team Coach emphasize?
Select an answer to reveal the explanation.
Short Explanation
A firehouse that runs twenty calls Saturday and zero Sunday is not a twenty-call department. Election-night reporting works the same way: one fat week does not mean the pipeline is predictable. Watch the swing, not the trophy week.
Full Explanation
SAFe flow predictability asks how consistently civic work finishes, not how loud one election-night reporting week looked. When throughput spikes then falls to zero, the coaching signal is variation: boom-and-bust weeks usually mean batching, unstable policies, hidden WIP, or demand that the workflow cannot absorb evenly. Emphasizing predictability and variation keeps leadership honest about whether the results pipeline can serve the public reliably, rather than celebrating a trophy week that will not repeat.
Averaging the spike with a zero week into one speed number fails by concept: it manufactures a false capacity claim and teaches the organization to plan from noise. Freezing the board after a high-throughput week fails by concept because it freezes learning and hides the next drop instead of improving the system that caused the swing. Replacing flow measures with story-point velocity fails by concept because points obscure wait, handoffs, and finish rates—the very signals a civic results team needs when election deadlines are real.
Exam caveat: SAFe flow metrics treat predictability and distribution as first-class coaching tools; a single throughput average is not a substitute for seeing variation. Throughput spikes can be legitimate seasonal demand, but they still do not define sustainable capacity without looking at the pattern over time.
Operational check: plot weekly throughput and flow time for the election-night reporting team across several weeks, show leadership the swing beside any headline week, and coach one concrete policy change (WIP limit, smaller batches, or earlier readiness) aimed at reducing variation before the next civic deadline.