CAPM · Question #28
How should a project manager plan communications for a project which has uncertain requirements?
The correct answer is A. Include stakeholders in project meetings and reviews, use frequent checkpoints, and co-locate team members only. For projects with uncertain requirements, agile communication practices - including stakeholder inclusion in meetings, frequent checkpoints, and team co-location - best support continuous alignment and rapid feedback.
Question
Options
- AInclude stakeholders in project meetings and reviews, use frequent checkpoints, and co-locate team members only.
- BInvite customers to sprint planning and retrospective meetings, update the team quickly and on a daily basis, and use official communication channels.
- CAdopt social networking to engage stakeholders, issue frequent and short messages, and use informal communication channels.
- DAdopt a strong change control board process, establish focal points for main subjects, and promote formal and transparent communication.
How the community answered
(55 responses)- A82% (45)
- B5% (3)
- C11% (6)
- D2% (1)
Why each option
For projects with uncertain requirements, agile communication practices - including stakeholder inclusion in meetings, frequent checkpoints, and team co-location - best support continuous alignment and rapid feedback.
When requirements are uncertain, including stakeholders directly in project meetings and reviews ensures continuous validation, frequent checkpoints enable rapid course corrections, and co-locating team members reduces communication latency - together these agile practices minimize the risk of misalignment caused by evolving requirements.
Referencing sprint ceremonies is agile, but requiring 'official communication channels' introduces formality that slows the rapid feedback loops needed when requirements are uncertain.
Using social networking and informal channels lacks the structured visibility and stakeholder accountability that a project with uncertain requirements requires to maintain alignment.
A strong change control board process and formal communication channels are predictive practices designed for stable requirements, not for adaptive environments where requirements are expected to evolve.
Concept tested: Communication planning for uncertain requirements in agile environments
Source: https://www.pmi.org/pmbok-guide-standards/foundational/agile-practice-guide
Topics
Community Discussion
No community discussion yet for this question.