PMP · Question #842
A project manager is managing a hybrid project. There is software in place to access the repository of project artifacts. However, a few stakeholders are reporting that they are unable to find the lat
The correct answer is B. Make sure all stakeholders have access to the system and know where to find project artifacts.. Stakeholders are unable to locate the project schedule despite a repository being available, indicating a communication management issue where access or knowledge of the system is lacking. The project manager should ensure proper access and guidance for stakeholders to find proje
Question
Options
- AAdvise the project management office (PMO) that there is a resource gap for sharing project
- BMake sure all stakeholders have access to the system and know where to find project artifacts.
- CEscalate the issue to the steering committee and ask them to deal with the stakeholders' lack of
- DSend the project schedule via email to the stakeholders who need that information.
How the community answered
(52 responses)- A12% (6)
- B81% (42)
- C6% (3)
- D2% (1)
Why each option
Stakeholders are unable to locate the project schedule despite a repository being available, indicating a communication management issue where access or knowledge of the system is lacking. The project manager should ensure proper access and guidance for stakeholders to find project artifacts in the designated system.
Advising the PMO of a resource gap is an overreaction; the issue is likely a communication or access problem, not a lack of resources for sharing.
This action directly addresses the root cause of the problem by ensuring stakeholders have both the necessary access to the artifact repository and the knowledge of how to navigate it to find information like the project schedule. It promotes self-service and consistent information access.
Escalating to the steering committee is an inappropriate first step for a common communication and access issue that the project manager should resolve directly.
Sending the schedule via email is a short-term workaround that doesn't solve the underlying problem of stakeholders being unable to use the designated repository for all project artifacts.
Concept tested: Communication management and information distribution
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
5B is correct, confirmed on exam last week. The PMBOK Guide Sixth Edition, Section 10.2.2.4, is explicit that project information flow depends on both system access and stakeholder awareness of where artifacts live. A and C escalate a minor access problem that the project manager owns outright, and D creates a secondary schedule copy outside the repository, which defeats the configuration management purpose. The right move is to fix the access gap and point stakeholders to the authoritative source.
B is right. PM owns artifact access and has to show folks where things live.
Confirmed B on my exam last month. The key is that the software already exists, so the PM just needs to make sure stakeholders have access and know where to look rather than creating a workaround like D.
D is a quick fix but kills transparency. B keeps the artifacts where everyone can self-serve.
Agreed on B. As a teacher I learned you have to show people where things are, not just put them somewhere.