Every month a temporary tiger team pulls parks Developers off recreation booking to rush a council demo elsewhere. What should the Product Owner show?
Select an answer to reveal the explanation.
Short Explanation
A monthly tiger-team raid is a fire drill that steals the crew from the actual park. Recreation booking cannot stay a product if its Developers keep getting yanked for demos. Show the continuity damage: lost focus, broken forecasts, and value that never compounds.
Full Explanation
Stable Scrum Teams compound product knowledge and flow; recurring raids reset both. When every month a temporary tiger team pulls parks Developers off recreation booking to rush a council demo elsewhere, Sprint focus, forecast reliability, and ongoing recreation-booking value are destroyed. The Product Owner should show that constant raids destroy product-team continuity and the ability to deliver ongoing value. Treating raids as utilization wins mistakes busyness for value and turns the product team into a spare-parts drawer for political demos.
Claiming raids increase utilization and therefore product value fails because utilization is not citizen value. Making tiger teams the only Scrum Team fails by replacing durable product ownership with demo fire drills. Inflating Sprint forecasts so raids look planned fails by hiding structural damage in the numbers instead of removing the raids.
Exam caveat: Recurring tiger-team raids are an org-design attack on product continuity and empiricism. Operational check: Quantify Sprints disrupted, forecast misses, and unfinished recreation-booking outcomes caused by raids, then ask leadership to staff demos without pulling the parks product team mid-stream.