HKSM

Identify Scrum Master and Business Stakeholder(s) is the initiation process that appoints a qualified Scrum Master and creates a clear, prioritized register of external business participants who influence, fund, use, or are affected by the product.

Purpose & When to Use

This process ensures there is a capable servant leader to run Scrum and a complete, prioritized list of business stakeholders to engage for direction, feedback, funding, and governance.

Use it at project start immediately after the Product Owner and vision are defined, and revisit whenever scope, funding, organization, or markets change (e.g., new regulator, new customer segment, vendor change, merger).

Mini Flow (How It’s Done)

• Confirm context and inputs: project vision, business case, organization chart, skills availability, budget/time constraints.
• Define Scrum Master selection criteria: facilitation and coaching skill, neutrality (not the Product Owner), availability, authority to remove impediments, knowledge of Agile/Scrum, and stakeholder management capability.
• Source candidates: internal pool, PMO/HR, agile coaches; interview for fit; confirm time commitment and authority; formally appoint the Scrum Master.
• Elicit business stakeholders: sponsor(s), customers and end-users, operations/support, sales/marketing, finance, legal/compliance, security/risk, data/privacy, procurement, vendors/partners, and impacted internal departments.
• Map and prioritize using a power–interest or influence–impact grid; define engagement strategies for high-priority stakeholders.
• Create a Stakeholder Register: name/role, organization, contact info, influence/interest, expectations, decision rights, availability/time zone, preferred channels, and key concerns.
• Validate with the Product Owner and sponsor; clarify boundaries: Scrum Team vs. stakeholders, how feedback flows through the Product Owner, and when stakeholders are invited to events (e.g., Sprint Review).
• Publish the register and engagement plan; schedule cadences (e.g., review demos, backlog input workshops); capture risks and constraints in the risk log.

Key outputs: appointed Scrum Master, approved Stakeholder Register, stakeholder engagement/communication plan, calendar invites for appropriate ceremonies.

Quality & Acceptance Checklist

• Named Scrum Master has confirmed availability, remit to remove impediments, and no conflict of interest (not also the Product Owner).
• Scrum Master understands the product context or has access to domain SMEs and coaching support.
• Backup/coverage plan exists for the Scrum Master’s absence.
• Stakeholder Register is complete and prioritized; includes decision-makers and actual end-users, not just managers.
• Roles and decision rights are clear (e.g., who can accept release outcomes, who controls budget, who approves compliance).
• Engagement approach documented: how stakeholders provide input, how often they attend reviews, and communication channels.
• Contact details, time zones, and availability constraints recorded; data privacy considerations addressed.
• Risks, assumptions, and constraints related to stakeholders logged and communicated.

Common Mistakes & Exam Traps

• Confusing Scrum Master with a task-assigning project manager; the Scrum Master facilitates and removes impediments rather than directing work.
• Assigning the Product Owner as Scrum Master (role conflict) or making the Scrum Master a part-time add-on without capacity.
• Ignoring external or regulatory stakeholders until late, causing delays in approval or compliance.
• Letting stakeholders bypass the Product Owner to change priorities directly with developers.
• Inviting stakeholders to the Daily Scrum; they are welcome at Sprint Review, not at internal team events.
• Listing departments instead of real people with decision rights and availability, leading to accountability gaps.
• Overlooking time zones and language needs, causing missed reviews and poor feedback.

PMP/SCRUM Example Question

During initiation, a sponsor asks who should be appointed now and who should be documented for engagement later. Which option best reflects the outcome of Identify Scrum Master and Business Stakeholder(s)?

1. Appoint the Product Owner now and list Scrum Team developers as stakeholders.
2. Appoint the Scrum Master now and create a prioritized register of customers, end-users, sponsors, and other external business participants.
3. Appoint both the Scrum Master and the entire Scrum Team now; defer stakeholder identification to the first Sprint Review.
4. Create a communication plan only; the Scrum Master can be chosen after the first Sprint.

Correct answer: B – This process appoints the Scrum Master and builds a prioritized Business Stakeholder register (customers, users, sponsors, compliance, vendors), enabling early engagement and clear decision pathways.