CAPM Practice: Determine how to conduct stakeholder communication

Changes to approved requirements require transparent, proactive communication to all affected parties. Stakeholders need to understand what changed, why, what the impact is, and how it will be managed — preventing surprises and building trust.

**Why not A:** Informing only the development team excludes stakeholders who approved the original requirement and may be affected by the change. Business stakeholders, sponsors, and other impacted parties need to understand why the change is needed, its implications, and how it will be managed.

**Why not B:** Waiting until the end of the iteration to communicate in the sprint review delays critical information. Requirement changes can affect ongoing work, priorities, and resource allocation. Proactive communication allows the team and stakeholders to adjust course before wasted effort accumulates.

**Why not D:** Making changes silently without informing stakeholders is a serious breach of trust and project governance. Undisclosed requirement changes can lead to misaligned expectations, scope disputes, and stakeholder dissatisfaction when the delivered solution differs from what was originally approved.