Certified ScrumMaster (CSM) — Questions 1–75

The most appropriate action is to help the team identify a small number of actionable improvements and ensure they are implemented. This directly addresses the frustration that nothing changes and demonstrates the value of the Retrospective. It also reinforces the Scrum principle of continuous improvement through inspect and adapt.

Facilitating a collaborative dialogue helps the Developers and Product Owner negotiate a realistic Sprint Backlog while balancing technical health. Product value and technical sustainability must coexist, and the Scrum Master guides the team to transparently forecast work without dictating technical solutions or bypassing the Product Owner's authority.

The Scrum Master must act as a guardian of the Scrum framework by preventing the misuse of metrics. Velocity is a team-specific tool for capacity planning, not an organizational performance measure. By educating the CEO on why velocity is a poor indicator of company success and suggesting more meaningful business outcomes, the Scrum Master provides a higher level of service to the organization and its leadership.

The Developers are self-managing and accountable for the Sprint Backlog, so they decide how to organize and assign work. The Scrum Master should explain self-management rather than assign tasks, ask the Product Owner to assign them, or create a rotating schedule. Coaching the team toward self-management supports Scrum's principles and builds long-term capability.

The Scrum Master must clarify that Velocity is a team-level metric for planning, not an individual performance measurement tool. Using it for evaluation damages morale and encourages behavior that inflates numbers rather than delivering value. The Scrum Master should educate the Product Owner on the dangers of this practice and suggest better ways to measure progress and value.

The Scrum Master serves the Scrum Team by facilitating collaboration and helping remove impediments, and here the impediment is a mismatch between new learning and the original plan. The Developers own the Sprint Backlog and may adapt it, while the Product Owner owns value and scope negotiation. Facilitating that conversation protects the Sprint Goal without overriding either role's authority.

The Scrum Master serves the team by ensuring they do not overcommit, which protects the team's sustainability and maintains the quality of the product. By coaching the team and the Product Owner to inspect their velocity and capacity, the Scrum Master facilitates a realistic plan. This is crucial because over-committing leads to technical debt and failed Sprint Goals, which undermines trust with stakeholders.

The Scrum Master should advise against extending the Sprint length, as fixed time-boxes limit risk and provide a predictable cadence for inspection and adaptation. Instead, the team should focus on improving estimation, refining backlog items, and reducing work in progress. Extending the Sprint reduces the frequency of feedback loops, directly undermining the empirical nature of Scrum and masking underlying delivery dysfunctions.

The Scrum Master serves the Scrum Team by coaching the Developers in self-management and cross-functionality. By facilitating sessions and removing impediments, the Scrum Master helps the team increase its effectiveness. These responsibilities are critical for building a high-performing team that can navigate complex work without needing external command-and-control management, which is essential for long-term project success and agility.

The Scrum Master serves the Product Owner by ensuring they can articulate the product's value and purpose. By facilitating workshops or coaching the Product Owner on vision-setting tools, the Scrum Master bridges the gap between technical work and strategic goals. This ensures that the entire Scrum Team and the stakeholders are aligned, which is a foundational requirement for successful product development in complex environments.

Revitalizing stale retrospectives requires introducing creative facilitation techniques and shifting the team's focus toward psychological safety and systemic impediments. By varying formats and addressing root causes rather than superficial symptoms, the Scrum Master helps the team unlock continuous improvement and higher engagement. This active coaching prevents routine fatigue and fosters a culture of genuine inspection and adaptation.

The Scrum Master serves the team by coaching it to turn Retrospective insights into small, testable actions owned by the Developers. Selecting a few high-impact improvements and defining concrete next steps makes follow-through likely and keeps ownership where it belongs. This reinforces continuous improvement and self-management rather than creating dependence on the Scrum Master or the Product Owner.

Serving the organization includes helping governance and funding practices become compatible with Scrum. Facilitating workshops with finance and portfolio leaders and coaching them to use Sprint Review evidence for funding decisions both increase organizational empiricism. The other choices either entrench annual planning, damage collaboration, or reduce transparency.

The Scrum Master must act as an organizational change agent. By coaching managers on the benefits of self-managed teams and the dangers of micromanagement, the Scrum Master helps create an environment where the team can thrive. This is essential for the Scrum framework to work, as the team must have full autonomy to plan and execute their work to achieve the Sprint Goal.

The Daily Scrum is a 15-minute time-boxed event solely for the Developers to inspect progress toward the Sprint Goal and adapt their plan. Detailed problem-solving sessions derail the focus of the event and should be deferred to a separate breakout discussion.

The Scrum Master serves the organization by helping it understand and apply Scrum effectively. When multiple teams build one product, separate backlogs and goals create integration and vision problems. The most appropriate first step is to facilitate awareness among Product Owners and stakeholders about the benefits of a single Product Backlog and a shared Product Goal, rather than imposing technical practices or taking over accountabilities.

The Scrum Master facilitates discussions about quality standards and ensures the Definition of Done is transparent and understood. By encouraging the team to continually raise the bar for quality, the Scrum Master helps eliminate technical debt and ensures a higher-quality product increment. This is vital for maintaining the team's agility and ensuring that the work produced is genuinely releasable, preventing hidden issues from accumulating over time.

The Sprint Retrospective is where the Scrum Team inspects its way of working and identifies the most helpful changes. To produce real change, the team should select a small number of high-impact improvements and incorporate them into the next Sprint's work. This converts retrospective insight into concrete action and builds a habit of continuous improvement rather than repeated venting.

The Daily Scrum exists to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, and it is timeboxed to 15 minutes. When technical debates consume the timebox, the Developers should end the event on schedule and continue detailed discussions afterward. This preserves both the timebox and the event's purpose without suppressing necessary technical collaboration.

The Daily Scrum is a 15-minute time-boxed event for the Development Team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. It is not a status report for management, but a tactical coordination meeting allowing developers to synchronize activities and plan their next 24 hours.

When a Sprint Goal loses its meaning due to drastic external changes, continuing the Sprint is pointless because the resulting work will not deliver value. The Product Owner holds the unique authority to cancel the Sprint and immediately initiate a new planning cycle based on updated priorities.

A Scrum-friendly culture is built on transparency, trust, and the continuous pursuit of improvement. By facilitating events, challenging ineffective policies, and encouraging collaborative learning, the Scrum Master helps the organization dismantle command-and-control habits. These efforts are vital because they create an environment where teams feel safe to experiment, learn from failure, and deliver value, which is the foundational purpose of adopting the Scrum framework within any professional setting.

The Scrum Master must help the organization understand Scrum's empirical approach. By shifting focus from fixed-date delivery to outcome-based progress, the Scrum Master educates stakeholders on the value of transparency and adaptation. This helps manage expectations while aligning with the reality of complex work, where scope and time are variables that must be managed through iterative inspection.

The Sprint Review is a collaborative event focused on the product increment and feedback, not a status report. If the team is just reading boards, they miss the opportunity to demonstrate value and gather meaningful feedback. The Scrum Master must pivot the team's focus toward demonstrating the actual product increment and facilitating a conversation with stakeholders to ensure the product's direction remains aligned with user needs.

The Sprint Retrospective is a required event that concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint and is attended by the entire Scrum Team. Its purpose is to inspect the last Sprint and create a plan for improvements to be enacted during the next Sprint, often including adjustments to the Definition of Done.

The Scrum Master is responsible for the health of the team and must address disruptive behavior. By coaching the individual in a private setting, the Scrum Master maintains psychological safety while directly addressing the issue. This is crucial because a healthy team dynamic is necessary for open communication, effective collaboration, and the sustained high performance that defines a truly successful Scrum team.

Self-management is a central tenet of Scrum. By delegating decision-making and encouraging collective accountability, the Scrum Master helps the team mature. These actions are vital because they shift the team's focus from waiting for instructions to proactive ownership of their work, which leads to higher engagement and better outcomes as they learn to manage their own process, tasks, and interpersonal dynamics.

The Sprint Review is the Scrum Team's opportunity to inspect the Increment with stakeholders and adapt the Product Backlog, and the Product Owner is accountable for maximizing value and ordering that backlog. When stakeholders bypass the Product Owner, the Scrum Master serves the team best by coaching the Product Owner back into that accountability, which restores a single channel for feedback and protects the Developers from unmanaged scope changes.

A new Product Owner needs guidance on prioritizing value and managing stakeholders. By coaching them on techniques like MoSCoW, ROI analysis, or impact mapping, the Scrum Master helps them turn a chaotic list of requests into a manageable, value-driven strategy. This support is crucial for building the Product Owner's confidence and ensuring they can focus on the most important work, rather than trying to please every stakeholder individually.

The Sprint Review is timeboxed to a maximum of four hours for a one-month Sprint. Its purpose is for the Scrum Team and stakeholders to inspect the Increment and adapt the Product Backlog. When discussions become lengthy and unfocused, the Scrum Master should coach participants on the event's purpose and help them manage the timebox, ensuring the event remains productive and within its limit.

The Developer must protect the integrity of the Sprint Goal and the Scrum process by referring the stakeholder to the Product Owner. The Product Owner is solely accountable for managing the Product Backlog and negotiating scope with stakeholders. This maintains the team's focus and ensures the Product Owner remains the single source of truth for work priorities, preventing scope creep and unmanaged disruptions.

The Product Owner holds the accountability for the release strategy and decision-making. Since the Product Owner manages the Product Backlog and maximizes value, they decide when and what to release. The Scrum Master must clarify this accountability to ensure the team understands their roles and maintains focus on their respective domains, preventing confusion about authority within the team.

The Scrum Master serves the Scrum Team by ensuring Scrum events are held, productive, and timeboxed, and by helping the team focus on high-value Increments that meet the Definition of Done. Ordering the backlog, selecting items, and authoring acceptance criteria belong to the Product Owner or the Developers, not to the Scrum Master.

The correct action is to coach the Developers to self-manage their Sprint Backlog and to help the Product Owner understand that the Developers own the 'how' of the work. This preserves the Product Owner's authority over product direction while restoring the team's autonomy, which is essential for Scrum to function.

The Scrum Master must act as a coach for the organization to protect the Scrum process. By teaching the Product Owner to defer new requests to the Product Backlog, the Scrum Master ensures the Development Team remains focused on the Sprint Goal. This preserves the integrity of the Sprint, prevents scope creep, and reinforces the accountability of the Product Owner for maximizing value through backlog prioritization rather than reactive, ad-hoc changes.

The Scrum Master serves the Scrum Team by coaching it toward effective collaboration and by helping it inspect and adapt its own processes. When one member is effectively excluded, the pattern belongs to the team, so the Scrum Master should surface it in a setting where the Developers can decide how to change. Private instructions or taking over the event shift ownership away from the team and do not build lasting self-management.

The Scrum Master serves the organization by helping it understand that Scrum replaces fixed-scope commitments with empirical forecasting. Educating finance and co-creating funding approaches that tolerate uncertainty preserves the team's ability to deliver value iteratively. The other actions either force predictive contracts onto the team or abandon Scrum, both of which undermine the organization's agility.

The Scrum Master must protect the team from external interference to ensure the Sprint Goal remains achievable. By coaching stakeholders on the role of the Product Owner, the Scrum Master establishes a clear channel for requirements, allowing Developers to focus on their commitments. This intervention is vital for maintaining velocity and ensuring the Scrum framework's integrity, preventing the team from being constantly derailed by ad-hoc, unplanned tasks.

Serving the organization during scaling means preserving Scrum's core: one Product Backlog, one Product Owner, and self-managing teams. Coaching the organization on these principles and facilitating lightweight coordination like a Scrum of Scrums supports scaling without reverting to command-and-control. The other actions fragment accountability, impose centralized control, or stifle team autonomy, all of which harm the organization's ability to deliver value.

The Scrum Master should facilitate the team's ability to address this behavior themselves. Instead of playing the role of a manager, the Scrum Master encourages the team to discuss the impact of the lateness. By focusing on the team's working agreements and the value of synchronization, the Scrum Master supports the team in upholding their standards without resorting to policing, which preserves the team's sense of self-governance and maturity.

The Scrum Master serves as a coach to improve team efficacy. By facilitating the creation of a 'Definition of Done', the Scrum Master helps the team establish a shared understanding of quality. These actions ensure that the product increment meets the necessary standards for release, reducing technical debt and increasing transparency, which is vital for empirical process control and long-term organizational value.

Demonstrating the value of Scrum is best achieved through results. By helping teams deliver working software that solves real user problems, the Scrum Master provides tangible proof of Scrum's effectiveness. This empirical evidence is far more convincing to stakeholders and leadership than any theoretical presentation, helping to build long-term buy-in and organizational commitment to the agile transformation process.

Focusing on the Scrum Values (Commitment, Focus, Openness, Respect, Courage) helps the organization build the right mindset to survive and thrive during change. Mechanics alone are often used in a superficial, cargo-cult manner that fails to produce real business outcomes. This service is essential because the values provide the internal compass that guides behaviors and decisions, ensuring that Scrum becomes a sustainable, effective way of working that drives real organizational transformation.

The Scrum Master must address this pattern because it prevents the team from planning and disrupts their rhythm. By coaching the Product Owner on the value of refinement and the necessity of planning even with an imperfect backlog, the Scrum Master ensures the team can continue their work. This prevents the Product Owner's lack of preparation from becoming an impediment to the team's ability to deliver value regularly.

The Scrum Master is responsible for coaching the team in self-management and conflict resolution. By fostering an environment of trust and open communication, the Scrum Master helps the team resolve issues independently. These actions are vital because unresolved conflict creates technical debt, reduces morale, and ultimately prevents the team from delivering high-quality, frequent increments of value as expected in the Scrum framework.

The Sprint Review is intended for inspecting the increment and adapting the Product Backlog, not for general backlog refinement. The Scrum Master must ensure the event focuses on collaboration and feedback regarding the product's progress. Correcting this misconception is crucial because the Sprint Review serves as the primary feedback loop between stakeholders and the team to ensure the product remains aligned with market needs.

The Daily Scrum is owned by the Developers, who may choose any structure or technique that keeps the event focused on progress toward the Sprint Goal and within fifteen minutes. Holding it at the same time and place each working day reduces complexity and supports a reliable habit, which is especially valuable for distributed teams. Neither extending the time-box nor converting the event into a status report is consistent with Scrum.

The Scrum Master must shift the team's focus from airing grievances to collaborative problem-solving. By introducing structured Retrospective techniques that prioritize actionable items, the Scrum Master helps the team move past the conflict. This is vital because Retrospectives are the engine for continuous improvement; without concrete actions, the team will remain stuck in a cycle of frustration and lack of progress, leading to disengagement and stagnation.

These actions directly address the systemic nature of an organizational transformation by promoting cultural shifts and process alignment. By focusing on transparency and empirical decision-making, the Scrum Master helps the organization move beyond individual team gains to broader institutional improvements. This work is essential to ensuring that Scrum is not just a localized project management tool but a robust organizational strategy for delivering consistent value and fostering continuous improvement throughout the enterprise.

The Daily Scrum is an internal inspection event for the Developers to synchronize activities and create a actionable plan for the next 24 hours. Because it belongs to them, external stakeholders do not dictate its agenda, and adherence to a strict rigid format is secondary to achieving synchronization and adaptation toward the Sprint Goal.

The Scrum Master must help the team understand that the Daily Scrum is for the developers to coordinate their work, not to report to the Scrum Master. By shifting the focus of the meeting, the Scrum Master promotes self-management. This is critical because reporting to a leader reinforces a traditional hierarchy, whereas planning together builds a collaborative team dynamic essential for Scrum success.

Scrum Masters coach teams toward self-organization rather than acting as command-and-control managers who resolve conflicts or assign blame. By facilitating root-cause problem solving and encouraging direct peer communication, the Scrum Master builds sustainable psychological safety. This empowers the cross-functional group to address systemic impediments independently and mature their internal collaboration dynamics over time.

The Sprint Retrospective is for the Scrum Team to inspect itself and plan improvements; the Scrum Master ensures it is positive and productive. The Product Owner may attend if invited but should not assign action items or lead the event, as that would undermine the team's self-management and ownership of its process improvement.

The Scrum Master serves the organization by leading, training, and coaching in Scrum adoption, which includes helping remove organizational barriers. When impediments lie outside the team's immediate sphere of control, the Scrum Master must champion the issue upward, working with organizational leaders to enact structural changes that enable high performance.

The Scrum Master serves the team by facilitating discussions on process improvement and encouraging the team to address impediments. Technical debt is a systemic issue that impacts the quality of increments. By guiding the team to include technical debt reduction in their planning, the Scrum Master helps the team align their work with the Definition of Done and ensures long-term sustainability of the product delivery process.

The Scrum Master serves the Scrum Team by ensuring Scrum is understood and enacted, and by coaching team members and the organization. The Daily Scrum belongs to the Developers, who may invite others if it helps them inspect progress toward the Sprint Goal. The Scrum Master's response is to coach the Product Owner on the event's purpose, not to bar attendance or escalate.

The Sprint Backlog is the plan by and for the Developers. While the Product Owner defines the goal and items, the Developers decide how to achieve that goal and create the plan. This ownership is crucial for self-management, as it empowers the team to commit to work they believe they can complete, fostering accountability and high-quality results throughout the Sprint.

The Daily Scrum is a brief, 15-minute event for Developers to synchronize their work and adjust their plan for the next 24 hours. It is critical for transparency and immediate adaptation. Understanding these two truths—that it is for the Developers and that it is for planning, not status reporting—is essential for maintaining the autonomy and focus of the Scrum Team during the Sprint.

The Scrum Master serves the organization by addressing systemic impediments like rigid procurement processes. Coaching procurement and legal on agile contract models and running a pilot can align procurement with Scrum without sacrificing governance. The other options either bypass policies, worsen rigidity with large fixed-price contracts, or use confrontational escalation, none of which foster sustainable organizational change.

The Scrum Master serves the organization by helping it understand and adopt Scrum-compatible practices. When an appraisal system rewards individual utilization over team outcomes, the Scrum Master should collaborate with HR and leadership to redesign it around team-based feedback and value delivery, rather than forcing the team to work around it or escalating punitively.

The Daily Scrum is a mandatory daily event owned by the Developers, used to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. When a team abandons it, the Scrum Master should coach them on its purpose and help them restore it. Allowing omission, escalating to the Product Owner, or substituting a weekly meeting all violate Scrum principles and fail to address the root cause.

The Scrum Master supports the Product Owner in finding techniques for effective Product Backlog management. This includes ensuring the Product Owner understands how to arrange the backlog to maximize value. This is a core competency because the Scrum Master acts as a coach to the Product Owner, ensuring the backlog remains a clear, ordered, and transparent tool for the team's work.

The Scrum Master must facilitate a dialogue about how this policy fundamentally blocks the core Scrum requirement of delivering a Done increment every Sprint. By presenting this as a systemic impediment, the Scrum Master helps the organization see the need to integrate security earlier in the development process. This service is critical because it moves the organization toward 'security as code' and continuous quality, rather than reliance on slow, batch-oriented gatekeeping processes.

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. This accountability is critical because it ensures the team maintains the transparency, inspection, and adaptation required for empirical process control, which ultimately leads to higher team performance and value delivery.

The Scrum Master must facilitate the transition by demonstrating how self-managing teams increase productivity and agility, ultimately reducing the need for traditional micro-management. By coaching management on the empirical process, the Scrum Master helps them shift focus from task management to value delivery. This service to the organization is crucial because it aligns internal structures with Scrum values, fostering a culture of accountability and transparency that empowers teams to deliver high-quality increments consistently.

The Scrum Master's role is to support the team in maintaining their Scrum events, but they should avoid being a 'policing' figure. By coaching the team to recognize the impact of late arrivals, the Scrum Master empowers the team to solve the problem themselves. This ensures the resolution is accepted by the group and addresses the root cause of the behavior, fostering accountability and mutual respect within the team.