Stakeholder Engagement and Communication
What to Know
Agile communication is frequent, transparent, and face-to-face where possible. Know the stakeholder map (power/interest), information radiators (visible boards, burn-down/burn-up charts), and feedback loops (Sprint Review, demos, user testing).
Communication channels: Daily Scrum (team), Sprint Review (stakeholders + team), Retrospective (team), and ad-hoc collaboration. The Product Owner is the primary conduit between stakeholders and the team. Osmotic communication - information absorbed by proximity - is a benefit of co-location.
Engagement principles: make work visible, invite stakeholders to Reviews, gather feedback early, and manage expectations with transparent forecasts rather than promises.
Traps
- "More documentation fixes communication." Prefer conversations and visible artifacts; documentation supports, not replaces.
- Stakeholders only at the end. Engagement is continuous, especially at Reviews.
- Hiding bad news. Transparency (e.g., a burn-up showing slippage) enables early correction.
- PO as a bottleneck - if the PO blocks all communication, feedback slows.
- Confusing the Review's purpose - it's for feedback and inspection, not a status report to management.
- Rich vs. lean channels - complex/ambiguous messages need richer (face-to-face) channels.
Rule of Thumb
Match channel to message: ambiguous or sensitive → rich, synchronous (face-to-face/video); simple and routine → lean, asynchronous (written). When in doubt, make it visible and invite feedback.
Worked Example
A stakeholder is surprised by a slipping timeline. The fix: a visible burn-up chart at each Sprint Review and a transparent forecast from the PO - engagement built into the cadence, not a late announcement.