CCNA Defining the Scrum Master / Team Coach Role Questions

The Retrospective exists for the team to inspect how it works and adapt its process, not to report status. By teaching the purpose and facilitating reflection on working agreements, flow, and collaboration, the Scrum Master / Team Coach restores the ceremony's intent and helps the team generate actionable improvements they own.

This is the correct first move because a Story stalled with no board updates usually signals an undisclosed blocker or a coordination gap. The Scrum Master / Team Coach's primary job is to surface and remove impediments, and a short, direct conversation with the people doing the work reveals the real problem before any process change is proposed. It also respects the team's self-management by not imposing a solution.

This is correct because it respects the team's autonomy while ensuring ART alignment. The Scrum Master / Team Coach facilitates a lightweight consultation with affected teams and the System Architect to surface dependencies and architectural concerns. This allows the team to decide with awareness of the broader system, reducing the risk of integration issues later.

Structured formats such as silent brainstorming, round-robin sharing, and dot voting change the mechanics of participation so quieter members contribute before discussion is dominated. Dot voting then lets the team, not the loudest voices, choose which improvement items matter. This is a direct application of the coach's facilitation skill and addresses both the participation imbalance and the weak improvement items.

PI Planning is the primary event where teams align with the ART. The Scrum Master / Team Coach ensures the team is prepared, understands dependencies, and contributes to program objectives. This helps the team see how their work supports the train's goals and builds cross-team collaboration, which is essential for ART integration.

The Scrum Master / Team Coach should first coach the individual privately. This addresses the behavior without embarrassing the developer, respects their enthusiasm, and reinforces the stand-up's timebox and purpose. It also models servant leadership by focusing on team improvement through individual coaching.

This protects the team from individual performance surveillance while meeting the manager's legitimate need for visibility. Team-level flow and Iteration progress are the meaningful measures in SAFe, and offering them reframes the request. It also models the coach's role in shielding the team from counterproductive reporting that undermines collaboration.

The Scrum Master / Team Coach is responsible for coaching the PO and team on role clarity. By privately coaching the PO to focus on value and priorities, and helping the team define technical decision rights, the SM addresses the root cause without undermining the PO in front of the team. This preserves psychological safety and reinforces self-management.

This is correct because the Retrospective is the team's own inspect-and-adapt event. By facilitating rather than directing, the Scrum Master / Team Coach helps the team generate and commit to improvements they own. Self-management grows when the team, not the coach, decides what to change. It also reinforces the SAFe principle of applying cadence and synchronization to continuous improvement.

Direct tasking bypasses the Product Owner, breaking the single-voice principle that governs backlog ordering. Coaching management to route every request through formal refinement restores that constraint, letting the Product Owner prioritise against iteration goals instead of developers absorbing unplanned work.

This addresses the root cause by changing how work flows through the team. Smaller Stories and earlier collaboration reduce batch size and handoffs, while a shared Definition of Done makes quality a whole-team responsibility. As Scrum Master / Team Coach, Marcus facilitates the team's agreement and helps it inspect whether the change improves flow, rather than fixing the environment for them or adding buffers.

This is correct because the Scrum Master / Team Coach should build the team's confidence and psychological safety to surface issues. Preparing and practicing beforehand helps the team articulate risks and dependencies clearly. Creating a safe environment encourages openness, which is essential for the ART to address problems early and adjust the plan.

The first step is to coach the team on inclusive facilitation and psychological safety. Techniques like round-robin, silent brainstorming, and inviting dissent ensure all voices are heard, which improves estimate quality and commitment realism. This directly addresses the root cause—dominance by a few and suppressed concerns—rather than applying a symptomatic fix like changing the meeting length or escalating to management.

Facilitating targeted retrospectives empowers the team to analyze root causes of friction and establish robust working agreements. This direct engagement builds trust, aligns the group around shared delivery goals, and addresses the systemic behavioral patterns hindering predictable value delivery across functional boundaries.

Coaching the team to resolve its own impediments and escalating only when necessary builds problem-solving capability and self-reliance. The Scrum Master remains accountable for removing impediments but should first help the team attempt removal. This graduated approach develops the team's ability to self-manage while ensuring blockers do not stall the Iteration unnecessarily.

This is correct because PI Objectives should express the value the team intends to deliver and include measurable outcomes, which enables the team and ART to track progress and adjust. The Scrum Master / Team Coach facilitates this by coaching the team on outcome-oriented language rather than simply listing features or tasks.

This is correct because the Retrospective is a primary mechanism for the team to inspect their process and decide on improvements. By coaching the team to own the Retrospective outcomes, the Scrum Master / Team Coach shifts decision-making to the team, fostering self-management. This builds the team's capability to solve problems without relying on the Scrum Master for direction.

Attending the ART Sync and using the Program Board are the primary SAFe mechanisms for cross-team coordination. The Program Board visualizes dependencies and milestones, while the ART Sync provides a forum to address them. Coaching the team to use these tools directly addresses late dependency discovery and builds the collaboration needed across the ART.

This approach tackles both issues: facilitation ensures balanced participation, and using historical velocity and capacity data helps the team make realistic commitments. The Scrum Master / Team Coach should intervene when one person dominates and guide the team to base commitments on evidence rather than optimism. This builds the team's ability to self-manage planning.

This addresses the behavior at its source while engaging the whole team in setting norms. Private coaching avoids public shaming, and co-created working agreements give everyone shared ownership of participation expectations. It fits the servant-leader and team-coach stance, building psychological safety and self-management rather than imposing a solution from above.

Working agreements are a core self-management tool that let the team define its own norms for collaboration and flow. When the team authors and owns them, adherence comes from shared commitment rather than imposed rules. This directly addresses interrupting, skipped refinement, and stalled Stories while building the team's capability to regulate itself.

A newly formed team lacks shared working agreements and trust. The Scrum Master therefore focuses on establishing norms, building psychological safety, and coaching the group toward self-organisation, which are the foundational conditions enabling effective Agile Team behaviour within SAFe.

Active listening lets the Scrum Master surface the team's own perspectives, and collaborative decision-making keeps ownership with the team rather than the leader. This directly satisfies the servant leadership behaviours sought during the SAFe transition, where the Scrum Master guides without commanding.

This action directly addresses the Product Owner's behavior while respecting their role. By coaching the Product Owner on how self-organizing teams pull work, the Scrum Master helps realign the team's operating model with SAFe principles. It also protects the developers from conflict and fosters a collaborative relationship. This is a servant-leader approach that resolves the root cause without undermining anyone's authority.

In SAFe, the Scrum Master / Team Coach helps the team make work visible and manage flow rather than absorbing hidden work. By surfacing the unplanned items, the team can see the real capacity consumed, decide whether to renegotiate scope with the Product Owner, and raise a systemic impediment if needed. This preserves team ownership and supports the Inspect and Adapt cycle without bypassing the team.

This action embodies the Team Coach role. By asking guiding questions and facilitating problem-solving, the Scrum Master helps the team build capability and confidence. Intervening only for external impediments respects the team's ownership of technical decisions. This approach aligns with servant leadership and self-organization, and it addresses the root cause of the team's inability to finish stories: over-reliance on the Scrum Master for technical direction.

This directly addresses the lack of follow-through by helping the team focus on a few impactful changes and creating accountability. The Scrum Master / Team Coach facilitates the team in choosing actions, assigning owners, and reviewing progress in subsequent events. This builds the team's ability to self-improve and makes the retrospective productive rather than repetitive.

Facilitating estimation and refinement helps the team uncover hidden complexities and reach a shared understanding of the work. This collaborative process leads to more accurate estimates and reduces the likelihood of overcommitment, aligning with the Scrum Master's role in promoting team-level flow and predictability.

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.

This approach builds the team's capability to self-manage by teaching problem-solving skills and progressively handing over responsibility. It aligns with the Scrum Master / Team Coach as a servant leader and coach, who should develop the team's autonomy rather than create dependency.

Coaching both the Product Owner and the team on backlog refinement addresses the root cause of unclear items. Refinement ensures stories meet the team's definition of ready before planning, reducing mid-Iteration churn and improving commitment quality. This is a core Scrum Master / Team Coach responsibility: building effective collaboration between the team and the Product Owner without taking over either role.

Rotating facilitation builds shared ownership of team events and develops facilitation skills across the team. It reduces reliance on the coach and encourages members to take responsibility for the quality of discussions and decisions. This is a practical way to grow self-management while keeping the coach available for deeper coaching and ART-level work.

Clearing blocks and reducing WIP is the most effective way to restore flow and reduce cycle time. By addressing the items that are stuck, the team can finish existing work before starting new tasks, which is the primary goal of managing flow in a SAFe environment.

This is correct because backlog refinement is a key collaboration point between the Product Owner and team. By coaching the Product Owner on refinement techniques, the Scrum Master helps ensure stories are well-understood and ready, reducing mid-Iteration confusion. This directly supports effective collaboration and aligns with the Scrum Master / Team Coach role in SAFe.

A private conversation with the technical lead addresses the behavior directly without embarrassing them, and coaching on facilitation supports a shift toward shared decision-making. This approach respects the lead's expertise while building a more inclusive team dynamic. It aligns with the Scrum Master's role of coaching individuals and teams to improve interactions and self-management.

This is correct because SAFe separates content authority from technical execution. The Product Owner owns what gets built and its acceptance criteria, while the team decides how to build it and demonstrates working software. A coach who takes on either task undermines those accountabilities. Explaining the boundary also educates the Product Owner and protects the team's self-management.

In SAFe, the Scrum Master / Team Coach is a servant leader and coach, not a people manager. This option correctly captures that the role builds team effectiveness through facilitation, teaching, coaching, and impediment removal, without assigning work or managing HR matters. That matches the responsibilities expected when onboarding a new Agile Team and explaining roles during the first retrospective.

The Scrum Master / Team Coach is responsible for coaching the team on Scrum and SAFe, helping them understand and apply practices, and guiding them to self-correct. This is a coaching accountability, not enforcement by authority. The role builds the team's capability to inspect and adapt rather than policing compliance, which aligns with servant leadership in SAFe.

This is correct because it addresses the root cause by making unplanned work visible and planning for it. The Scrum Master / Team Coach should help the team and Product Owner collaborate to reserve capacity for support, which improves predictability and reduces overcommitment. This is a proactive, data-driven approach.

Facilitating a team-building session on psychological safety and shared norms directly addresses the low trust and blame culture. It helps the team establish working agreements and practice constructive conflict resolution. This action creates a safe environment for open discussion, which is essential for effective retrospectives and continuous improvement. It aligns with the Scrum Master's role as a coach and facilitator of team health.

Smaller stories reduce risk and variability because they are easier to estimate and complete within a short time-box. By coaching the team to slice stories vertically and thinly, the Scrum Master helps create a more consistent flow of value, which is the foundation of predictability in an Agile environment.

As teams mature, the Scrum Master / Team Coach role evolves from removing impediments to coaching advanced technical practices and fostering broader collaboration. This helps the team continue improving and contributing to the ART's success. The other options either revert to a command-and-control approach, introduce unnecessary process overhead, or focus on individual performance rather than team growth.

This is correct because the situation calls for transparency and adaptation, not heroics. By helping the team and Product Owner re-forecast and consider descoping, the coach keeps the Iteration Goal meaningful while protecting sustainable pace. It also models the SAFe principle that scope and time trade off, and that the team owns how much work it can realistically complete with reduced capacity.

This is correct because ART Sync is a key event for coordinating across teams, and the Scrum Master / Team Coach should help the team engage in it. By encouraging participation, the team can surface dependencies and risks early, improving flow and alignment. This directly addresses the lack of cross-team collaboration while respecting the team's autonomy.

The Scrum Master / Team Coach should help the team turn reflection into action by limiting improvements to a few, assigning owners, and following up. This builds the inspect-and-adapt habit and makes the Retrospective meaningful. It directly addresses the lack of carried-forward actions while preserving team ownership of the improvements rather than imposing solutions from outside.

The Scrum Master / Team Coach serves the team by helping it create its own working agreements and then building the skills to honor them. A facilitated conversation about rotation keeps the decision with the team, spreads facilitation experience across members, and develops the self-management SAFe relies on. Coaching individuals afterward ensures the rotation actually works rather than becoming a formality.

Facilitating balanced participation draws out the technical risks and dependencies that only the developers can identify. By helping the team incorporate that input into its plan and Iteration Goals, the Scrum Master / Team Coach improves the realism of the PI plan and strengthens the team's ownership of its commitments.

Establishing direct communication channels between teams enables proactive dependency management and aligns delivery schedules across the Agile Release Train. Scrum Masters act as servant leaders who remove impediments by connecting interdependent teams to foster shared ownership.

This action directly supports the Scrum Master's responsibility to help the team understand its role in the ART. By linking Iteration Goals to PI Objectives and showing how team events integrate with ART events, the Scrum Master builds context and alignment. It also reinforces the cadence and synchronization that are core to SAFe, without taking over the team's own decision-making or the RTE's facilitation duties.

Using a structured retrospective format and steering the team toward a small number of concrete improvements directly addresses the loss of improvement focus. The Scrum Master's role is to facilitate the team's self-assessment and help them commit to actionable changes. This approach preserves team ownership while restoring the Retrospective's purpose, which is continuous improvement rather than status reporting.

Introducing a structured format that emphasizes team interactions and process helps shift the focus from individual status to collective improvement. Coaching the team to avoid status reporting reinforces the retrospective's purpose. This action aligns with the Scrum Master's role as a facilitator who guides the team toward inspect-and-adapt. It also provides a safe framework for reflection, which is essential for continuous improvement in SAFe.

Asking probing questions is a powerful coaching technique that helps the team think critically about their integration points. This facilitates the discovery of dependencies without the Scrum Master doing the work for them, ensuring the team remains accountable for their own plan and commitments.

This action addresses the underlying issue by exploring why the team cannot find time and helping them adjust their plan or working agreements. It keeps ownership with the team and uses the Scrum Master's coaching skills. By facilitating root-cause analysis, the Scrum Master helps the team discover their own solution, which is more sustainable than imposing one. This aligns with the servant-leader role and the SAFe principle of applying cadence and synchronization.

This is correct because the team is meeting goals but may be working on lower-priority items due to backlog ordering. The Scrum Master / Team Coach should facilitate collaboration between the Product Owner and team to review and adjust the backlog ordering based on business value. This addresses the root cause without disrupting the team's delivery cadence.

This action aligns with the Scrum Master's role as a facilitator who promotes balanced participation and helps the team achieve its objectives. Techniques like round-robin or silent brainstorming create space for quieter members, while an explicit prompt about dependencies addresses the risk. It keeps ownership with the team and models inclusive collaboration. The Scrum Master remains a servant leader by enabling the team rather than directing it, and the focus on dependencies supports ART-level coordination.

The Scrum Master facilitates the refinement process, ensuring the team and PO are aligned before PI Planning. This preparation is critical because it allows the team to plan effectively during the event, identifying risks and dependencies early rather than spending the time trying to understand the work.

Synchronization is the core of the Team Sync. By sharing progress and identifying blockers daily, the team can adjust their plan in real-time. This ensures that the team remains focused on the Iteration Goal and that any issues are raised and addressed before they become major delays.

This directly builds self-management by transferring ownership of decisions the team is capable of making. Coaching questions prompt reflection rather than answers, a strong Definition of Done removes ambiguity about completion, and allowing technical debates to resolve within the team grows capability. It preserves accountability while reducing the coach as a dependency.

Facilitating a reflection on past PI Objectives and their causes helps the team learn and make more realistic forecasts. This approach addresses the fear by focusing on facts and improvement rather than blame. It aligns with the Scrum Master's role of coaching the team toward transparency and continuous improvement during PI Planning.

This is correct because the root cause is taking on unrefined stories. A Definition of Ready helps the team and Product Owner agree on criteria for stories to be considered ready for Iteration Planning. The Scrum Master / Team Coach should coach the team to apply it during refinement, improving predictability and reducing mid-Iteration surprises.

The Scrum Master / Team Coach should facilitate a safe and productive Sprint Review. By intervening to structure the feedback and protect the team from personal attacks, the SM ensures the event remains focused on inspecting the product and adapting, while maintaining psychological safety.

This directly addresses the team's uncertainty while preserving the Scrum Master/Team Coach's ART responsibilities. A visible escalation path and a designated backup ensure impediments still get removed when the coach is unavailable. It also reinforces team self-management rather than dependency on one person, which aligns with the servant-leader stance in SAFe.

Calculating true available capacity ensures that team commitments are grounded in realistic operational realities. The Scrum Master guides the team to account for interruptions transparently, fostering predictable execution and accurate forecasting for the broader Agile Release Train.

Coaching the team to plan against historical velocity and its true capacity is exactly the teaching-and-facilitating work of the Scrum Master / Team Coach. The role does not assign work or dictate estimates; it helps the team see its own data, understand the cost of unused capacity, and improve its forecasting. Facilitating Iteration Planning keeps ownership with the team while building the skill they currently lack.

This is correct because the coach makes the pattern visible to the team and offers lightweight facilitation techniques that change the dynamics without blaming anyone. Structured turn-taking and silent brainstorming give quieter members space to contribute while still using the lead's expertise. It respects the team's ownership by inviting them to decide whether and how to adjust how they work together.

This action helps the team understand how to translate Features into actionable Stories and measurable Iteration Goals, which is essential for creating realistic PI Objectives. Coaching during the event enables the team to learn by doing, which is a core responsibility of the Scrum Master / Team Coach in SAFe.

Facilitating a transparent capacity discussion grounded in historical velocity and upcoming time off lets the team itself recognise the overcommitment and renegotiate scope, which is the Scrum Master's servant-leadership responsibility rather than dictating the commitment.

TDD and Pair Programming are key Built-in Quality practices. They ensure that code is tested as it is written and that multiple eyes review the logic, which significantly reduces defects. The Scrum Master's role is to coach the team on these benefits and facilitate the time needed to learn them.

The System Demo is an inspect-and-adapt event, and the Scrum Master / Team Coach helps the team use feedback constructively. Comparing the Definition of Done with stakeholder expectations reveals whether the DoD is too narrow, whether acceptance criteria were ambiguous, or whether the stakeholder's mental model was wrong. Capturing the gap as an improvement item turns a public challenge into a concrete change the team can act on.

Collaborating with the Release Train Engineer and peers ensures that systemic impediments identified during Inspect and Adapt are visible at the program level. This enables structured cross-ART problem-solving and aligns leadership toward permanent organizational fixes.

Servant leadership includes modeling the behaviors the team has agreed to, and private coaching respects individuals while addressing specific gaps. Arriving early and prepared demonstrates commitment without lecturing, and one-on-one conversations let the coach understand root causes such as overload or unclear expectations. Together with the retrospective discussion, this builds the team's ownership rather than imposing compliance from outside.

Servant leadership in SAFe means enabling the team to self-organize by facilitating the creation of its own working agreements. Co-creating agreements builds ownership, and modeling the behaviors reinforces them. This action directly supports the Scrum Master / Team Coach responsibility to coach the team in self-management and foster a healthy team culture.

The Daily Stand-up is an inspect-and-adapt event for coordinating work and surfacing impediments, not a design meeting. Coaching the team to keep it focused and parking deep discussions for afterward preserves the timebox while ensuring blockers are visible. This improves flow and lets the coach address systemic impediments with the ART.

This action directly addresses the team's concern by returning decision authority to the team and redefining the Scrum Master's role as a facilitator and coach. It preserves the team's self-management while allowing the Scrum Master to provide technical guidance only when requested. This aligns with the SAFe Scrum Master/Team Coach responsibility to build high-performing, self-organizing teams and reinforces psychological safety.

Coaching through questions builds the team's capability to self-organize and own their process. In SAFe, the Scrum Master / Team Coach fosters an environment where the team makes decisions rather than depending on a single authority. This approach aligns with servant leadership and accelerates the team's maturity across Iterations.