PMP Practice: Keep the Vision Current

Chidera Nwosu is leading a project at Entropy Spark Corp to redesign their flagship mobile game with both new content releases (developed iteratively) and backend infrastructure upgrades (delivered in phases with strict dependencies). During the kickoff, the marketing director insists the vision should emphasize 'rapid feature launches to capture market share,' while the engineering lead argues for 'architectural stability and technical debt reduction.' The product owner wants to focus on 'player experience and retention metrics.' After the kickoff, Chidera notices that team members are confused about priorities—developers are arguing about whether to refactor legacy code or build new features first, and the marketing team is frustrated that engineering 'doesn't understand urgency.' What should Chidera do to address this misalignment?