Completing one building-permit citizen journey requires the Product Owner to coordinate six component teams for forms, payments, identity, GIS, notifications, and records. Handoffs stall value every Sprint. What should the Product Owner advocate?
Select an answer to reveal the explanation.
Short Explanation
Six pit crews for one bicycle is not craftsmanship — it is a traffic jam. If one citizen journey needs a parade of handoffs, the org design is the bug. Build a team that can finish the ride, not a prettier relay baton.
Full Explanation
Component-aligned teams optimize for technical layers and create dependencies that the Product Owner then has to heroically coordinate. That structure lengthens Time-to-Market and weakens empiricism because no single team can produce a valuable Done Increment for the journey. Advocating a feature or value-stream team design is an organizational-design intervention in the Product Owner’s interest. Adding program ceremony or splitting the Product Goal into component goals institutionalizes the handoff problem.