City digital services organizes teams by department systems such as tax, licensing, and utilities, so a resident moving to the city must complete four disconnected journeys. What should the Product Owner promote?
Select an answer to reveal the explanation.
Short Explanation
Residents do not experience “the tax system” and “the licensing system.” They experience moving to the city, and the org chart currently chops that journey into four queues. Align teams to the citizen value stream so one product effort can finish the move, not the department’s database.
Full Explanation
Team boundaries that mirror internal systems force Product Owners to coordinate handoffs across a citizen journey. Value-stream alignment—such as a “move to the city” journey—lets a cross-functional team deliver a coherent Increment of resident value. Liaison committees and component teams around legacy databases preserve the fragmentation. Organizational design should follow how citizens experience outcomes, not how departments store records.