A legacy mainframe replacement for utility billing has a detailed project plan and no Product Vision. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A project plan says how to move the boxes. A vision says why residents should care after the boxes move — accurate bills they can understand, fewer shutoff surprises. Replacement work is still a product.
Full Explanation
Even replacement programs create a product that users will live with. A project plan describes activities, dates, and scope; it does not state the citizen outcome that should guide trade-offs when the plan meets reality. The Product Owner should establish a Product Vision so ordering decisions optimize value, not merely task completion. Without that vision, the team can finish the project and still leave residents worse off.