HKSM

Individuals or groups outside the core Scrum Team who have a business interest in the product, such as customers, users, sponsors, and subject matter experts. They provide needs, priorities, and feedback to guide value delivery. They are identified early, engaged throughout, and their list is maintained as an input and output across Scrum processes.

Key Points

• People with a business interest in the product, not part of the core Scrum Team.
• Typical roles include customers, end users, sponsor, marketing, sales, legal, support, and compliance.
• Identified early and recorded in a Stakeholder Register; updated as the product evolves.
• Primary channel of interaction is through the Product Owner; engagement is facilitated by the Scrum Master.
• Act as an input to product visioning, backlog creation, prioritization, and Sprint Review feedback.
• Outputs include updated stakeholder lists, clarified needs, and validated increments that influence backlog ordering.

Purpose

Business stakeholders bring the voice of value, funding, and market reality. Their insights shape the product vision, epics, and user stories, and their feedback validates increments during reviews.

Effective engagement ensures the team builds the right thing, reduces rework, and supports rapid decision making on scope and release priorities.

Key Terms & Clauses

• Stakeholder Register: a living list of business stakeholders with roles, interest, influence, availability, and contact details.
• Engagement Strategy: how the Product Owner and Scrum Master plan touchpoints, feedback loops, and decision paths.
• Interest-Influence Mapping: simple view to prioritize engagement effort and escalation routes.
• Voice of Customer: mechanisms like interviews, surveys, and demos to capture needs and satisfaction.
• Acceptance and Validation: stakeholder participation in Sprint Review to confirm value and uncover new needs.

How to Develop/Evaluate

Start by identifying all parties affected by or able to affect the product: sponsor, key customers, user groups, and enabling functions. Document names, roles, expectations, decision authority, and preferred communication channels in the Stakeholder Register.

Evaluate completeness and quality by checking coverage of all business areas, clarity of decision rights, and availability for reviews. Revisit the list at major milestones, new releases, or organizational changes.

How to Use

Use business stakeholders as inputs when creating the project vision and developing epics and user personas. The Product Owner channels their needs into user stories, estimates value, and orders the Product Backlog.

During release planning and backlog refinement, incorporate stakeholder priorities and constraints. Invite relevant stakeholders to Sprint Reviews to validate increments and provide feedback that updates the backlog.

As an output, updates to the stakeholder list and their feedback flow into refined acceptance criteria, reordered backlog items, and improved engagement strategies for future sprints.

Example Snippet

Sample Stakeholder Register entries:

• Customer Group A - High interest, high influence; expects simplified onboarding; attends monthly release reviews.
• Sponsor - High influence; approves release goals; prefers concise dashboards before major decisions.
• Compliance SME - Medium influence; provides regulatory constraints; engaged prior to release cut-off.
• Support Lead - Medium interest; provides insights on defects and adoption; participates in Sprint Review Q&A.

Risks & Tips

• Risk: bypassing the Product Owner leads to conflicting direction and churn. Tip: route requests through the Product Owner.
• Risk: missing key stakeholders causes late compliance or market surprises. Tip: review and update the register frequently.
• Risk: too many voices in planning slow decisions. Tip: define decision authority and escalation paths up front.
• Risk: irregular feedback leads to misaligned features. Tip: schedule predictable Sprint Review participation.
• Risk: stakeholder availability gaps. Tip: secure time commitments and backup delegates early.

PMP/SCRUM Example Question

During a Sprint Review, several business stakeholders provide conflicting priorities for upcoming user stories. What is the best next step?

1. Ask the Scrum Master to decide the final order of the Product Backlog.
2. Have the Developers vote to lock the next sprint scope immediately.
3. The Product Owner consolidates stakeholder input and reorders the Product Backlog based on value and risk.
4. Invite all business stakeholders to the Sprint Retrospective to resolve the conflict.

Correct Answer: C — The Product Owner consolidates stakeholder input and reorders the Product Backlog based on value and risk.

Explanation: The Product Owner owns backlog ordering and stakeholder engagement. The Scrum Master and Developers do not decide priority, and stakeholders do not attend the Retrospective.