3.8. Plan and Manage Communication
💡 First Principle: A communication plan only works if it creates a genuine feedback loop — broadcasting status updates without a mechanism for stakeholders to respond and be heard fails the "transparency and collaboration" standard PMI tests here.
Enablers: define a communication strategy, promote transparency and collaboration, establish a feedback loop, understand reporting requirements, create reports aligned with sponsor/stakeholder expectations, and support reporting/governance processes.
The distinction from Task 3.4 (Engage Stakeholders) matters again here: this task is the mechanics — cadence, channel, format, audience-tailored reports — that support the relationship work happening elsewhere. A report that satisfies a governance requirement but doesn't answer what the specific stakeholder audience actually needs to know fails this task's intent even if it's technically "sent on time."
Building the communication plan
Planning runs in a fixed order: define the strategy and audiences, identify each audience's reporting requirements, establish a feedback loop, then execute and adjust based on the feedback. The communications management plan answers, per audience, why the information is shared, what is shared, how — the method and channel — and when and how often. The strategy for each stakeholder follows from their power, interest, engagement level, preferences and cultural context.
⚠️ Exam Trap: Stakeholders give feedback on communications, but they do not edit the communication plan — the project team owns it and updates it through its own process. An option asking "how can stakeholders change the plan?" describes something the plan does not contain.
Complexity grows faster than headcount. The number of communication channels is n(n − 1) / 2: a team of 10 has 45 channels, and adding five people raises it to 105. That arithmetic is why large programs segment audiences rather than broadcasting to everyone.
Push, pull and interactive
| Method | How it works | Examples |
|---|---|---|
| Push | Sent to recipients without them asking | Emailed status reports, newsletters |
| Pull | Placed where recipients retrieve it when they choose | Intranet pages, wikis, shared repositories |
| Interactive | Real-time, multi-directional exchange | Meetings, video calls, workshops |
Interactive is the richest and best for resolving ambiguity; pull suits large audiences with varied needs; push suits information someone must receive whether or not they go looking for it.
Agile communication: face to face and visible
One of the 12 Agile Principles states that face-to-face conversation is the most efficient and effective way to convey information to and within a development team. Hence agile favors colocation and frequent face-to-face contact over weekly meetings and email chains. Colocation also enables osmotic communication — information flowing into the background hearing of team members, who pick up what they need without being directly addressed. Even a remote sponsor who prefers email should be encouraged to spend some time with the team for face-to-face contact and access to visual information.
Information radiators — highly visible charts and boards in the team area — carry transparency. When a business representative asks for the latest defect count, take them to the radiator rather than producing a one-off answer. When executives demand lengthy weekly reports that eat delivery time, invite them to the sprint review and point them to the radiators.
⚠️ Exam Trap: "Produce the report they asked for" or "assign someone to write weekly reports" looks like good service. In an agile setting the keyed answer redirects stakeholders to the existing sources of truth — reviews and radiators — which are more current and cost the team nothing extra.
Distributed teams
When colocation is impossible, recreate its benefits with tools and habits: group messaging, video or phone stand-ups, electronic Kanban boards and backlogs. Build cohesion by pairing team members and rotating the pairs. Across time zones, combine asynchronous communication — shared documents, threaded discussions, decision logs — with short synchronous touchpoints, set protocols in the team charter, and rotate meeting times so the inconvenience is shared fairly rather than always falling on one location.
Transparency, even when it hurts
Honesty is a PMI Code of Ethics standard, and it outranks short-term comfort. A PM who discovers a defect just before a critical review tells the stakeholder, explains the fix and its minor delay, and offers to review the rest now or reschedule slightly — never hides it or disguises it with a workaround. Transparency can also make things look worse before they get better: complaints rising after a more open reporting plan often mean previously hidden issues are finally visible. That is the plan working.
⚠️ Exam Trap: Choosing the most detailed/comprehensive report format as the "best practice" answer. PMI usually rewards the format tailored to what that specific audience needs to decide or act on — more detail isn't automatically better communication.
Reflection Question: Recall a status report you produced that technically met a governance requirement but didn't actually serve the audience's real information need. What would a better-tailored version have looked like?
