Identified Scrum Master
Identified Scrum Master is the named individual selected to serve as Scrum Master for a Scrum Team on a specific project or release. It is an Initiate-phase output that becomes a key input to planning, facilitation, coaching, and impediment-removal activities across the Scrum lifecycle.
Key Points
- Formal output of the Initiate phase, typically from the Identify Scrum Master and Stakeholders process.
- Recorded with name, time allocation, authority boundaries, and start date.
- Becomes an input to release planning, sprint planning, daily standups, sprint reviews, and retrospectives.
- Must be neutral to scope and prioritization decisions and should not be the Product Owner.
- Empowered to remove impediments and uphold Scrum values and practices.
- Often dedicated to one team; supporting more than one team requires careful capacity checks.
- Works closely with the Product Owner and Scrum Team to facilitate flow and continuous improvement.
Purpose
The primary purpose is to ensure a clear, accountable facilitator is in place to guide Scrum events, coach the team, and remove impediments quickly. This enables predictable sprint execution, adherence to Scrum, and a single contact for process-related issues.
Confirming this role early reduces startup delays, clarifies responsibilities, and provides leadership continuity throughout release and sprint cycles.
Key Terms & Clauses
- Servant leadership: Focus on enabling the team, not directing work.
- Neutrality: Avoids prioritization and scope authority held by the Product Owner.
- Impediment management: Owns the impediment log and escalation paths.
- Facilitation: Schedules and runs Scrum events and fosters collaboration.
- Empowerment and access: Clear authority to engage stakeholders and escalate blockers.
- Availability: Time commitment matched to team needs; avoid overloaded assignments.
- Backup arrangement: Named delegate for continuity during absences.
How to Develop/Evaluate
Identify candidates during initiation with input from the sponsor, PMO, HR, and the Product Owner. Evaluate facilitation skills, coaching mindset, conflict resolution ability, knowledge of Scrum, and capacity to serve the team.
Check for conflicts of interest (for example, avoid assigning the Product Owner or someone with strong delivery authority over the team). Confirm empowerment and availability, document the appointment, and communicate it to all stakeholders.
Set initial working agreements, agree on escalation channels, and plan onboarding steps such as tooling setup and event cadence.
How to Use
Treat the Identified Scrum Master as a required input to early planning and team formation. The Scrum Master facilitates release planning, sprint planning, and ceremonies, maintains the impediment log, and coaches the team and Product Owner.
Leverage the role to promote transparency (Scrumboard, information radiators), ensure Definition of Ready and Definition of Done clarity, and to drive continuous improvement via retrospectives.
In scaled settings, the Scrum Master may also participate in Scrum of Scrums to coordinate dependencies and cross-team impediments.
Example Snippet
Initiate phase record:
- Name: Alex Kim.
- Role: Scrum Master, Team Alpha.
- Time allocation: 100%.
- Authority: Empowered to escalate impediments to Sponsor and engage external teams.
- Responsibilities: Facilitate Scrum events, maintain impediment log, coach team, uphold Scrum practices.
- Start date: 10 Mar 2025. Backup: Jamie Lee.
Risks & Tips
- Risk: Assigning a part-time Scrum Master to multiple teams leads to delayed impediment removal. Tip: Match capacity to the number of teams and workload.
- Risk: Conflicts of interest if the same person is also Product Owner or line manager. Tip: Separate roles to preserve neutrality.
- Risk: Lack of empowerment stalls decisions. Tip: Document escalation paths and sponsor support.
- Risk: Inexperienced facilitator. Tip: Provide coaching, mentoring, or training early.
- Risk: Mid-sprint role changes. Tip: Arrange a named backup and transition checklist.
- Risk: Overfocus on tools or metrics over people. Tip: Emphasize coaching, collaboration, and outcomes.
PMP/SCRUM Example Question
During initiation, the team is asked to start sprint planning next week, but no Scrum Master has been appointed. What should the Product Owner do?
- Ask a senior developer to run sprint planning temporarily and proceed.
- Have the project manager act as Scrum Master for the first sprint without formal appointment.
- Ensure the Scrum Master is formally identified as an output of initiation before scheduling sprint planning.
- Cancel the sprint and pause the project until release planning is complete.
Correct Answer: C — Ensure the Scrum Master is formally identified as an output of initiation before scheduling sprint planning.
Explanation: Identified Scrum Master is an initiation output and an input to facilitation of planning events. Proceeding without a formally appointed Scrum Master risks poor facilitation and unclear accountability.
HKSM