PK0-004 · Question #1033
During a meeting, a key stakeholder hears about a new project and immediately demands the sponsor provide weekly progress reports. The project manager quickly informs the sponsor that the…
The correct answer is B. The project charter does not provide the stakeholder with authority. The project charter formally defines the roles, responsibilities, and authority levels of stakeholders on a project. If the charter does not grant a particular stakeholder the authority to demand weekly reports, the project manager can confidently decline that demand. The…
Question
During a meeting, a key stakeholder hears about a new project and immediately demands the sponsor provide weekly progress reports. The project manager quickly informs the sponsor that the stakeholder does not need a weekly report. Which of the following explains how the project manager reached this conclusion?
Options
- AThe project manager reviewed the stakeholder register.
- BThe project charter does not provide the stakeholder with authority.
- CThe stakeholder is not on the meeting minute distribution list.
- DThe project manager reviewed the risk register.
How the community answered
(18 responses)- A17% (3)
- B72% (13)
- C6% (1)
- D6% (1)
Explanation
The project charter formally defines the roles, responsibilities, and authority levels of stakeholders on a project. If the charter does not grant a particular stakeholder the authority to demand weekly reports, the project manager can confidently decline that demand. The stakeholder register (A) tracks communication preferences and engagement levels but does not define authority. The distribution list (C) is irrelevant to authority, and the risk register (D) tracks risks - neither determines who has decision-making power over reporting requirements.
Topics
Community Discussion
No community discussion yet for this question.