New to the July 2026 exam? Read what changed in the 2026 PMP exam.

People: Stakeholder Engagement and Communication

Engaging stakeholders through structured analysis, aligning and managing expectations, planning communications, and ensuring effective knowledge transfer.

5 minutes 5 Questions

Stakeholder Engagement and Communication is a critical people domain competency in the PMP framework, emphasizing the project manager's ability to identify, analyze, and actively manage relationships with all individuals or groups who can influence or be affected by the project. **Stakeholder Iden…

Concepts covered
Managing Stakeholder Expectations in Complex EcosystemsStakeholder Identification and AnalysisStakeholder Engagement StrategiesAligning Stakeholder Expectations with Project ObjectivesCommunication Planning and MethodsActive Listening and Feedback TechniquesCross-Cultural Communication in Global ProjectsVirtual Collaboration Tools and TechniquesNegotiation and Influence SkillsStorytelling and Presentation in Project CommunicationKnowledge Transfer and Lessons LearnedManaging Communications in Agile Environments
Test mode:
Start practice test

PMP - People: Stakeholder Engagement and Communication Example Questions

Test your knowledge of People: Stakeholder Engagement and Communication

Question 1

A project has just concluded, and the team has completed a comprehensive lessons learned register documenting key insights, challenges, and recommendations for future similar projects. The project manager must now determine how to maximize the value and accessibility of this knowledge for the organization. What is the most appropriate approach to managing the lessons learned register?

Correct Answer: Store the lessons learned register in the organizational process assets (OPA) library, ensure it is easily searchable and accessible to all project teams, and communicate its availability to relevant stakeholders so future projects can apply these insights.

Lessons learned are organizational knowledge assets that should be systematically captured, stored, and made readily available to improve future project performance. According to PMBOK standards, lessons learned documentation must be retained in the organizational process assets library where it can be accessed, searched, and referenced by current and future project teams. The key is making it accessible and discoverable—not restricting access, requiring approvals, or mixing it with project closure documents. The correct approach involves three critical elements: proper storage location (OPA), appropriate accessibility (available to all teams), and active communication (stakeholders must know it exists). This ensures the documented knowledge creates organizational learning and continuous improvement across projects.

Question 2

A remote team keeps its shared cloud folder tidy, but members still waste time hunting for the latest files because names like 'final', 'final2', and 'newfinal' appear across many documents. Which practice would best help members locate the right version quickly?

Correct Answer: Adopt a consistent file-naming convention that includes dates and version numbers

A consistent file-naming convention with dates and version numbers gives every document a clear, sortable identity so members instantly recognize the latest version.

Keeping personal local copies fragments information and worsens version confusion. Increasing storage only lets the team pile up more duplicates without solving identification. Weekly video calls reading out changes are inefficient and rely on memory rather than a durable, self-explanatory system.

Key concept: configuration and version management through standardized naming conventions to ensure information accessibility and traceability.

Question 3

An agile software team is integrating their product with a hardware component supplied by an external vendor. The vendor operates using traditional project management methods, relying on monthly formal status reports. The agile team relies on daily syncs and bi-weekly iteration reviews. This mismatch is causing confusion and delays in shared deliverables. What should the project lead do to align communication between the two entities?

Correct Answer: Facilitate a joint workshop to create a hybrid communication plan that accommodates both the vendor's formal reporting needs and iterative feedback cycles.

Facilitating a joint workshop to create a hybrid communication plan fosters collaboration and ensures the needs of both the agile software team and the traditional hardware vendor are appropriately met.
Requiring the vendor to transition to agile is unrealistic and oversteps operational boundaries. Relying solely on monthly updates ignores the agile team's need for frequent alignment. Amending the contract to mandate attendance is coercive and does not organically solve the fundamental communication gap.
Key concept tested: Tailoring communication strategies across hybrid project environments.

More People: Stakeholder Engagement and Communication questions
2752 questions (total)
Practice 100 questions
One session at a time, always new questions