Stakeholder Engagement
Identify, analyse, engage
Stakeholder identification starts early and is revisited, not frozen at chartering. Use a power/interest grid to choose engagement style: high power and high interest get close partnership; low power and high interest get regular information; high power and low interest get concise summaries and no surprises. A communication plan in Agile is lightweight and adaptive - it names who needs what, when, and through which channel, and it changes as the project does.
Artefacts that build shared understanding
Understand how vision statements, product boxes, personas, user stories with acceptance criteria, wireframes and prototypes create a shared picture. Information radiators and colocated team spaces enable osmotic communication. The sprint review is the primary engagement event: an inspection of working software with genuine dialogue, not a one-way demo. Effective teams keep a single prioritisation voice - usually the product owner - while letting all stakeholders be heard.
Traps
- Choosing "send a weekly status email" when the question asks how to build shared understanding.
- Making the project manager the sole conduit between stakeholders and team, or "shielding" the team from stakeholders - engagement beats protection.
- Escalating a stakeholder disagreement before those involved have talked directly.
- Treating the review as a presentation with no feedback or backlog change.
Rule of thumb: replace written status with visible artefacts plus direct conversation. If stakeholders disagree, bring them together around the working increment and let the facts, not memos, settle the debate.