The city merges its parks reservation app and its recreation-class registration app into one product, but conflicting old slogans still appear in stakeholder decks. What should the Product Owner do first?
Select an answer to reveal the explanation.
Short Explanation
Two apps became one product — that is one map, not two bumper stickers. Old slogans that point opposite directions just confuse staff and residents. Publish one vision, retire the contradictions, then order the backlog against that single story.
Full Explanation
When the city merges parks reservation and recreation-class registration into one product, conflicting old slogans in stakeholder decks must be retired. The Product Owner should publish one unified Product Vision for the merged parks-and-recreation product first so ordering and communication share a single destination. Keeping both slogans and two Product Goals so neither department feels it lost preserves conflict inside the new product. Archiving the merged Product Backlog until marketing finishes a brand campaign delays value work for messaging. Splitting the Scrum Team so each former app keeps its original vision and release calendar undoes the merger's product intent. Exam caveat: merger of products requires merger of vision before dual branding continues to drive dual backlogs. Operational check: draft and socialize one vision covering booking and class registration outcomes, remove contradictory slogans from decks, and reorder a single backlog against the unified direction. Merged parks-and-recreation products require one unified vision before dual slogans keep driving dual backlogs and calendars. Retire contradictory deck language and reorder a single backlog against the shared destination.