Courseiva

SSM Defining the Scrum Master / Team Coach Role Practice Question

A SAFe Scrum Master / Team Coach is coaching a team that has recently adopted SAFe. Which TWO actions best exemplify the servant-leader behavior expected in this role? (Choose two.)

⚠ Common exam trap

Test-takers frequently confuse servant leadership with permissiveness or with taking over team decisions; true servant leadership means enabling the team's self-organization and removing obstacles, not directing work or bypassing team conversations.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

✓

Coaching the Product Owner on effective backlog refinement and helping the team improve their estimation and forecasting techniques.

Servant leadership in SAFe involves removing impediments and coaching the team and Product Owner to improve. Removing blockers, whether directly or by escalation, enables the team to focus on value delivery. Coaching the PO and team on refinement and estimation enhances the system. In contrast, assigning tasks, deciding story selection, or escalating performance issues without discussion are command-and-control actions that undermine self-organization and trust.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✓

    Coaching the Product Owner on effective backlog refinement and helping the team improve their estimation and forecasting techniques.

    Why this is correct

    Coaching the Product Owner and the team is a key servant-leader behavior. By helping the PO with backlog refinement and the team with estimation, the Scrum Master improves the system in which the team works. This supports better planning and delivery without taking over decision-making. It reflects the Scrum Master's role as a teacher and mentor, and it aligns with SAFe's focus on continuous improvement and cross-functional collaboration.

  • ✗

    Making final decisions on which stories to include in the Iteration to avoid conflicts during Iteration Planning.

    Why it's wrong here

    Deciding which stories to include is the team's and Product Owner's responsibility, not the Scrum Master's. Taking over this decision would disempower the team and violate self-organization. The Scrum Master should facilitate the planning process, not dictate its outcomes. This action also undermines the Product Owner's authority over backlog prioritization. Servant leadership means enabling others to decide, not deciding for them.

  • ✗

    Escalating individual team members' performance issues to their functional manager without discussing them first with the team.

    Why it's wrong here

    Skipping direct conversation and immediately escalating to a functional manager damages trust and bypasses the team's ability to self-correct. The Scrum Master should first coach the team member and facilitate a constructive conversation. Escalation may be necessary in some cases, but doing so without any prior discussion is not servant leadership. This action also blurs the line between the Scrum Master role and people management, which in SAFe is typically handled elsewhere.

  • ✗

    Assigning each team member their daily tasks to ensure the Iteration plan is followed precisely.

    Why it's wrong here

    Assigning tasks is a command-and-control behavior that contradicts servant leadership and self-organization. In SAFe, teams are empowered to manage their own work. The Scrum Master should facilitate the team's ability to self-organize, not dictate tasks. This action would undermine ownership and motivation, and it is not part of the Scrum Master role. It also ignores the principle that the team is best positioned to decide how to accomplish its goals.

  • ✓

    Removing impediments that the team identifies during the Iteration, such as resolving a blocked environment or escalating a dependency to the Release Train Engineer.

    Why this is correct

    Removing impediments is a core servant-leader behavior. The Scrum Master helps the team by clearing obstacles so they can focus on delivering value. This includes both direct removal (e.g., fixing a blocked environment) and escalation (e.g., to the RTE for cross-team dependencies). It demonstrates service to the team and the ART, and it aligns with SAFe's emphasis on relentless improvement and flow. It does not involve directing the team's work.

About these practice questions

One of 385 original SSM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written and reviewed by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint

This SSM practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SSM exam.