Traditional project management says you need a communications management plan. Agile says transparency happens by default through frequent touchpoints. Who's right? The answer: both—depending on what you're delivering. The dolphin-and-submarine metaphor explains why.
The Dolphin and the Submarine
Imagine tracking a dolphin versus a submarine. Dolphins surface frequently—you can usually see where they are. Submarines stay underwater for months, maybe years. You might not see them again until they choose to surface.
Agile projects are dolphins. Predictive projects are submarines.
A submarine dives after kickoff and stays submerged through long stretches of analysis and design. Only at milestones does it surface to reveal progress. Between those moments, stakeholders must trust that the plan is executing. That's why submarine projects need solid communications management plans—to bridge the silence.
Agile projects surface every two weeks. They demonstrate working increments. They discuss blockers and adjust course. There is no long silence to bridge.
What Agile Uses Instead
Agile doesn't eliminate communication. It embeds it into the rhythm of delivery.
Frequent demos replace progress reports.** Stakeholders attend a demo and see working software instead of reading a monthly status email.
Kanban boards replace status meetings.** Anyone can see what's in progress, queued, and complete. Modern tools calculate lead time, cycle time, and throughput automatically.
Information radiators replace formal reports.** Teams display cumulative risk scores, velocity charts, and impediment lists on shared screens. Information stays visible—not locked in a document reviewed once a month.
Where the Metaphor Breaks Down
Agile teams still need to communicate beyond their rituals. Executives, customers, and external stakeholders don't always attend sprint reviews. They need updates framed in business terms.
A product backlog visible to the team isn't useful to a CEO who wants to know if the product will launch on time. Someone still needs to translate agile outputs into stakeholder-friendly narratives.
Our Analysis
The absence of a formal communications management plan in agile projects isn't a gap—it's a feature. Agile practices create structured communication opportunities that don't require a document to execute. Transparency comes from ceremony, not documentation.
The mistake some teams make is treating "we're agile" as an excuse not to communicate with stakeholders outside ceremonies. If your product owner attends every sprint review, fine. If your CEO sees you quarterly, you still need to give them something useful.
Who should care:
- Project managers transitioning to agile** — Learn to translate outputs, not report inputs.
- Scrum masters and coaches** — Ensure ceremonies produce genuine dialogue, not status theater.
- Executives and sponsors** — Demand stakeholder-appropriate summaries, not "just trust the process."
- Hybrid teams** — Watch for reporting cadences that satisfy both agile delivery and traditional governance.
What to watch:** How hybrid governance models create reporting cadences that satisfy agile teams and traditional stakeholders simultaneously.
Key takeaways
- Agile projects surface frequently (dolphins); predictive projects disappear for long stretches (submarines)
- Demos, Kanban boards, and information radiators replace formal communications plans
- External stakeholders who don't attend ceremonies still need tailored updates
- Transparency comes from ceremony rhythm, not documentation
Frequently asked questions
Why don't agile projects need formal communications management plans?
Agile ceremonies—demos, retrospectives, stand-ups—create structured communication that replaces static documentation. The rhythm itself becomes the plan.
What are information radiators?
Large displays showing project data—velocity, risks, impediments—visible to team and stakeholders at all times. Information stays live, not archived.
How do you keep executives informed without formal reporting?
Translate agile outputs into stakeholder-appropriate summaries. Executive demos or one-page progress snapshots work better than detailed documentation.
Can agile teams have communication problems too?
Yes. If stand-ups become status updates, demos become show-and-tell, and retros become complaint sessions, the communication rhythm breaks down—and the transparency benefit disappears.