The snow-route operations team hides slipped stories until the iteration review. What should the Team Coach promote?
Select an answer to reveal the explanation.
Short Explanation
Hiding a slipped plow-route story until Friday is like covering the pothole with snow. The Team Coach makes work, gaps, and repeat misses visible while there is still time to adapt. Green boards that lie are worse than an honest yellow.
Full Explanation
On a snow-route operations team, the Scrum Master / Team Coach promotes transparency of work, outcomes, and recurring misses throughout the iteration—not only at the iteration review. Hiding slipped plow-route stories until Friday prevents mid-iteration adaptation and conceals systemic problems that residents feel as uncleared routes. Visible work is how the team and ART can inspect and improve while there is still time to act.
Keeping a private coach-only log of slips fails because it protects stakeholder comfort at the expense of honesty and blocks collective problem-solving. Moving every slipped story into the IP iteration so the current iteration still looks green fails because parking overflow for optics falsifies delivery status and delays learning. Replacing the iteration review with a utilization report that omits unfinished stories fails because busyness metrics without unfinished work are transparency theater.
Exam caveat: transparency includes bad news; green boards that lie are worse than an honest yellow for public-works credibility. Operational check: make slipped snow-route items visible on the team board as soon as they slip, discuss blockers in team sync, keep unfinished work in the review conversation, and track recurring misses as improvement inputs rather than end-of-iteration surprises.