Business analysts in the building-permits bureau sit outside the Scrum Team writing specification packets, then throw them over the wall to Developers who never meet applicants. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Specs thrown over a wall go stale before the first permit screen is built. Discovery belongs in the same team that will ship, like a chef tasting the soup instead of reading a memo about it. Pull analysis into the Scrum Team so permit learning is not a handoff.
Full Explanation
When analysis lives only outside the Scrum Team, discovery is separated from delivery and empiricism suffers. Specification packets recreate a phase-gate model and keep Developers away from applicants whose outcomes define permit value. The Product Owner should integrate discovery and analysis capacity into the team so refinement, ordering, and learning happen together. A separate analysis Sprint or a complete-up-front packet is the old structure with new labels.