Stakeholders and collaboration in agile teams
Domain 2 examines stakeholder identification, analysis, and engagement in agile teams, plus the collaboration practices and role boundaries the exam expects you to distinguish. It tests judgement: who to involve, when, and through which channel.
Identify and analyse
Use the stakeholder onion to scan the team, the business, and the wider environment-users, sponsor, operations, support, compliance, suppliers, and regulators. Then analyse power, interest, impact, and attitude (champion, supporter, neutral, critic). The Product Owner represents product value but not every stakeholder; a BA helps ensure voices are not filtered out.
Collaborate deliberately
- Whole-team approach: shared understanding through conversation, not handoffs.
- Three amigos-business, development, testing-shape stories and acceptance criteria together.
- An empowered, available Product Owner enables fast decisions; 'on-site customer' is the XP analogue.
- Use demos, workshops, story-mapping sessions, retrospectives, and information radiators as collaboration, not reporting.
- Maintain a lightweight engagement plan: stakeholder, decision needed, cadence, channel, owner.
- For distributed teams, make communication explicit and artefacts visible; do not assume osmotic communication.
Role boundaries
The PO owns value and ordering; the BA supports analysis, facilitation, and elaboration; the Scrum Master removes impediments; the team owns delivery. When the BA becomes a middleman, feedback slows and distortion increases.
Worked example
A compliance officer joins late, with high power and high interest, and is sceptical. The BA invites them to a story-mapping workshop, adds regulatory acceptance criteria to affected stories, and schedules quarterly demos. Reasoning: high power/interest alone suggests 'manage closely', but attitude and timing determine the tactic. Early involvement turns a critic into a reviewer and prevents late rework.
Traps
- Consulting only the Product Owner and calling that stakeholder engagement.
- Ignoring indirect stakeholders such as operations, support, and audit.
- Assuming co-location or that email equals collaboration.
- Letting the PO filter all feedback instead of exposing the team to users.
- Producing a stakeholder grid and never acting on it.