PMP Practice: Analyze communication needs of all stakeholders

In a hybrid project, stakeholders need to understand how different approaches work together toward common objectives. The VP's concern is legitimate—she's receiving information that appears contradictory because the communication approach doesn't clearly explain how the predictive and adaptive components relate to each other. An integrated communication approach that distinguishes between fixed commitments and adaptive elements, while showing how both serve the overall timeline, addresses the root cause. This allows executives to understand the certainty around go-live dates while accepting that software features evolve based on user feedback within that timeframe. The communication method should match the project's hybrid nature rather than treating the components as completely separate efforts.

**Why not A:** Explaining agile principles to the VP addresses her knowledge gap but not her actual problem. She needs to understand how the hybrid project communicates progress coherently, not receive a lecture on why scope changes are normal. Education alone does not solve the communication design problem.

**Why not B:** Shifting the entire project to a predictive approach eliminates the benefits of adaptive software development and contradicts the sponsor-approved hybrid methodology. The software team's stable velocity shows the agile approach is working; the issue is how progress is communicated, not how work is being executed.

**Why not D:** Creating two separate communication streams isolates information and prevents executives from seeing the full picture. If the VP receives only milestone reports and the software team's stakeholders receive only sprint reviews, nobody has an integrated view of how both components support the overall go-live date.