CAPM Practice: Determine how to conduct stakeholder communication

The stakeholder register captures stakeholder information (roles, interests, influence), while the communications management plan documents what information each stakeholder needs, how often, and in what format.

**Why not A:** A work breakdown structure (WBS) decomposes project deliverables into smaller work packages for scope management. It does not capture stakeholder communication preferences, contact information, or communication frequency needs — those are documented in the stakeholder register and communications management plan.

**Why not C:** The project charter authorizes the project and identifies high-level objectives, constraints, and key stakeholders, but it does not detail individual communication needs or preferences. It is a founding document, not a communication planning tool.

**Why not D:** A requirements traceability matrix (RTM) tracks requirements from origin through implementation and testing. While it references stakeholders as requirement sources, it does not document their communication preferences, channels, or frequency needs.