Public works, parks, and the clerk's office each run a separate report-a-problem app with overlapping citizen journeys. What should the Product Owner recommend?
Select an answer to reveal the explanation.
Short Explanation
Three city apps that all say "report a pothole" is three kitchens cooking the same soup. Consolidation is one Product Vision and one Product Owner so residents are not guessing which door to knock on. Extra portals and a shared Scrum Master do not fix the duplicate.
Full Explanation
Duplicate municipal products waste portfolio capacity and confuse users. When public works, parks, and the clerk’s office each run a separate report-a-problem app with overlapping citizen journeys, residents guess which door to knock on while three teams rebuild similar flows. The Product Owner should recommend consolidating the duplicates under one Product Vision and a clearly accountable Product Owner. Sharing a Scrum Master standardizes events without resolving product identity. Popularity of branding is not a substitute for a value-based product boundary.
Keeping all three apps and adding a fourth comparison portal fails by adding another layer of confusion. Letting each department keep its app but share a Scrum Master fails because ceremony standardization does not fix duplicate product identity. Ranking the three apps by brand-color popularity in a resident poll and keeping only the winner’s code fails by treating branding taste as product strategy.
Exam caveat: Consolidate overlapping civic apps under one vision and one Product Owner. Operational check: Choose a single report-a-problem Product Vision, name one Product Owner, migrate overlapping journeys, and retire or redirect the duplicate department apps.