The transit-app Scrum Team waits a month in a shared-services user-experience queue before any fare-flow experiment can be designed. What should the Product Owner argue?
Select an answer to reveal the explanation.
Short Explanation
A month in the UX waiting room is a month the fare app cannot learn. Scarce skills parked in a shared queue look efficient and feel like a traffic jam. Embed the skill in the Scrum Team when the product cannot deliver without it.
Full Explanation
Shared-service queues for scarce skills such as user experience create delay that damages Time-to-Market and Ability to Innovate. When that skill is critical to fare-app value, the Product Owner should argue for embedding it in the Scrum Team rather than optimizing specialist utilization in a central pool. Product Owner-written interface specs or annual redesign projects do not restore rapid inspection with riders. Embed when the wait is structural, not merely occasional.