Skip to content
PMPMedium

PMP Practice: Ensure Shared Vision with Stakeholders

Question 3 of 20 in Develop a Common Vision

Pepper Lindström-Ali is leading a project for Coral Reef Fintech to develop an AI-powered content moderation tool. The client, a social media platform, has expressed concern that emerging regulations around digital safety may significantly change their requirements within the next six months. The executive sponsor wants the project managed using a traditional waterfall approach because 'that's how we've always done enterprise software projects.' However, three weeks into requirements gathering, the stakeholder group has already proposed fifteen conflicting feature priorities, and the legal team warns that two different regulatory frameworks may take effect during the project timeline. The product owner and development team are requesting more flexibility to adapt as regulations become clearer. What approach should Pepper recommend to best ensure all stakeholders maintain a shared vision throughout the project?
Show answer & explanation

Correct answer: Propose a hybrid approach where high-level compliance requirements are baselined using predictive planning, but feature development occurs in two-week adaptive cycles with regular vision-alignment workshops involving all stakeholder groups

Explanation

This scenario presents competing stakeholder expectations, significant external uncertainty from pending regulations, and conflicting feature priorities — all indicators that a hybrid approach would best maintain stakeholder alignment. The project has legitimate reasons for structure (enterprise software, compliance requirements) but also compelling reasons for adaptability (regulatory uncertainty, evolving requirements). A hybrid approach respects the sponsor's need for governance and predictability around compliance baselines while giving the team flexibility to adjust features as regulations clarify. Regular vision-alignment workshops directly address the task of developing and maintaining a shared vision when stakeholder perspectives differ. The key closing facts are the conflicting priorities, regulatory uncertainty timeline, and the team's explicit request for flexibility — together these make hybrid the clearly superior choice over pure predictive or pure agile.

**Why not A:** Switching entirely to an agile framework dismisses the sponsor's legitimate need for predictability around compliance requirements. Regulatory uncertainty does not negate the need for structured governance, and telling the sponsor that predictive planning is impossible ignores the well-defined compliance aspects of the project.

**Why not B:** Proceeding with waterfall and adding monthly steering committee meetings does not provide the flexibility the development team needs to adapt to evolving regulations. Monthly updates cannot keep pace with regulatory changes that may emerge every few weeks, and this approach ignores the team's explicit request for flexibility.

**Why not C:** Creating a comprehensive requirements traceability matrix and obtaining formal sign-off assumes requirements can be fully defined upfront. With fifteen conflicting feature priorities and two uncertain regulatory frameworks, locking down requirements before beginning design would create a rigid plan based on incomplete information.

Key Concept

This question covers Ensure Shared Vision with Stakeholders under Develop a Common Vision (People).

Share:

This is 1 of 100 free PMP questions

Unlock 6,300+ PMP practice questions with detailed explanations, progress tracking, and exam readiness prediction.

Unlock All Questions