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.

ICS/OT Cybersecurity Fundamentals — Security Built for Industrial Systems

Industrial control systems cannot be secured like ordinary IT. A forced reboot, aggressive scan, or incompatible patch can interrupt production and create real safety consequences. Effective OT security begins with understanding the systems, constraints, and risks unique to industrial environments.

This course gives IT professionals, engineers, operators, and security practitioners a practical foundation in ICS threats, zone and conduit design, risk assessment, passive asset visibility, and vendor evaluation. You will learn how IEC 62443, NIST CSF, and MITRE ATT&CK for ICS apply where availability and safety come first.

Eight reconstructed incidents—including Stuxnet, Triton, Ukraine 2015, Colonial Pipeline, and PIPEDREAM—show how attackers move through OT environments, what they target, and which defenses could have changed the outcome.

Watch the course preview, then build the vocabulary, frameworks, and judgment needed to take credible first steps in ICS/OT cybersecurity.

Explore the Course


ICS/OT Cybersecurity Fundamentals course preview

Write the OT incident plan your site will actually use

Go from a blank page to an approved, usable plan for your industrial site, one chapter at a time. ICS/OT Incident Response Plan: Write One That Works includes 50 videos, the plan template, worksheets and a full model answer, delivered through HKSM Courses for US$147 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course