HKSM
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?
- Selected Scrum Master, identified business stakeholders, and a Task List created by decomposing committed user stories during Sprint Planning.
- A finalized product roadmap and release plan for the next three quarters.
- A signed vendor contract and procurement statement of work.
- 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.
