Identify Scrum Master and Business Stakeholder(s) process

This process selects the Scrum Master and identifies the business stakeholder representatives by applying agreed selection criteria. It also converts the committed user stories into concrete, actionable tasks that are recorded in a Task List, with task identification taking place during the Sprint Planning meeting.

Key Points

  • Use predefined selection criteria (e.g., facilitation skill, experience, availability, neutrality) to choose the Scrum Master and designate business stakeholder representatives.
  • Define responsibilities, decision authority, and collaboration expectations for the Scrum Master and stakeholders.
  • During Sprint Planning, break down committed user stories into specific tasks and compile them into a Task List.
  • Primary outputs: named Scrum Master, stakeholder roster, and an initial Sprint Task List derived from the committed stories.

Example

A software team reviews selection criteria and appoints Dana as Scrum Master due to her facilitation background and availability. They identify stakeholder reps from Marketing and Compliance to provide business input. In Sprint Planning, the team decomposes a committed story "As a user, I can reset my password" into tasks: design flow, build API endpoint, update UI, write unit tests, create email template, and verify acceptance criteria, then adds these tasks to the Task List.

PMP Example Question

Which outcome best fits the Identify Scrum Master and Business Stakeholder(s) process?

  1. Selected Scrum Master, identified business stakeholders, and a Task List created by decomposing committed user stories during Sprint Planning.
  2. A finalized product roadmap and release plan for the next three quarters.
  3. A signed vendor contract and procurement statement of work.
  4. A comprehensive risk register with quantified risk responses.

Correct Answer: A — Selected Scrum Master, stakeholder list, and Task List from story decomposition

Explanation: This process focuses on appointing the Scrum Master and stakeholder reps using selection criteria and transforming committed user stories into tasks during Sprint Planning to form the Task List.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Seven sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Stop Managing Admin. Start Leading the Future!

HK School of Management helps you learn AI prompt engineering for project work. Move beyond status reports and risk logs with practical prompt frameworks for everyday tasks. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Enroll Now