Certified ScrumMaster (CSM) — Questions 226–300

The Scrum Master should facilitate a conversation between the Developer and Product Owner rather than making a unilateral decision. The Definition of Done is a shared commitment that must be understood and agreed upon by the entire Scrum Team. By facilitating, the Scrum Master ensures transparency and alignment, which are critical for the team to consistently deliver increments that meet the quality standards of the product.

The Scrum Master serves the organization by helping it create an environment where transparency and continuous improvement are possible. A blame culture discourages people from surfacing problems, which undermines Scrum's empirical approach. Coaching the organization to look at the system and process when defects occur helps build safety and supports the team's ability to inspect and adapt.

The Daily Scrum is the Developers' event to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. When it becomes a status report to the Scrum Master, the Scrum Master should coach the Developers on its purpose and help them reclaim ownership. This supports self-management and empiricism rather than imposing control or changing the framework.

Scrum requires that the Scrum Team adapts to its environment while maintaining the core accountabilities and events. When synchronous meetings are difficult, the team must find a way to meet the purpose of the event—alignment and progress tracking—without necessarily relying on a rigid, live daily call. The focus must be on keeping the team informed and ensuring the work remains transparent to everyone.

The Scrum Master should facilitate a conversation between the Developers and the Product Owner to ensure technical debt is made transparent in the Product Backlog. This is a critical leadership act because ignoring technical debt leads to a decrease in development velocity and quality over time. By balancing new features with necessary refactoring, the team maintains a sustainable pace and long-term delivery capability.

The Scrum Master acts as a servant leader by facilitating self-organization and resolving impediments without taking direct command. Coaching the individual on collaborative behavior helps preserve team autonomy while addressing disruptive dynamics. This matters because a healthy Scrum Team relies on psychological safety and shared ownership rather than autocratic technical dictation by a single dominant developer.

The Daily Scrum is a strict fifteen-minute timeboxed event for the Developers to synchronize activities and create a plan for the next twenty-four hours. Lengthy technical deep-dives derail the meeting and exclude other team members. The Scrum Master should remind the participants to park the discussion and schedule a separate follow-up session immediately after.

The Scrum Master serves the organization by coaching it on Scrum and helping it understand that progress is inspected at the team and product level, not through individual hour tracking. Offering Sprint Goal progress and increment information meets the manager's need for visibility while protecting the team's collective accountability and trust.

The Scrum Master must act as an advocate for the principles of Scrum. While meeting audit requirements is necessary, they should not compromise the integrity of the Scrum framework. By working with the audit team to find ways to satisfy requirements through transparency and empirical evidence rather than traditional documentation, the Scrum Master protects the team while ensuring the organization stays compliant with its legal obligations.

Sprint Planning is a collaborative event where the Scrum Team defines the Sprint Goal (Why), selects Product Backlog items (What), and plans how to deliver them (How). It is timeboxed to eight hours for a one-month Sprint and may be shorter for shorter Sprints. The Sprint Backlog produced is a living plan that the Developers update as they learn.

The Scrum Master serves the Scrum Team by coaching self-management and facilitating the team's own inspection and adaptation. Coaching the Developers on how the Sprint Goal guides daily decisions, and helping them choose an improvement in the Retrospective, both build the team's capability to manage its own work. Assigning work, policing via the Product Owner, or editing the Sprint Backlog all substitute external control for self-management.

The Developers own the Sprint Backlog and are solely responsible for estimating their capacity and crafting the Sprint Goal. When they realize capacity is insufficient, they must collaborate with the Product Owner to adjust the scope of the Sprint Backlog before finalizing the plan, ensuring the Sprint Goal remains achievable without lowering quality standards or forcing unauthorized overtime.

The Scrum Master serves the organization by helping it understand that Scrum is built on team-level accountability. Instead of supplying individual utilization data, the Scrum Master should educate HR and collaborate on performance approaches that reinforce collaboration and value delivery. The other options either comply with a harmful request, refuse unhelpfully, or shift the burden to the team without addressing the root conflict.

The Scrum Master serves the organization by helping everyone understand Scrum roles and the importance of a single Product Backlog. When a stakeholder bypasses the Product Owner, the Scrum Master should coach both the stakeholder and the Product Owner on proper channels. This protects the team's focus and reinforces the Product Owner's accountability for ordering the backlog.

The Sprint Review is a collaborative event for inspecting the outcome of the Sprint and adapting the Product Backlog. It is the perfect opportunity to align expectations based on the work actually completed. By acknowledging the stakeholder's input and updating the Product Backlog, the Product Owner maintains transparency and ensures the stakeholder's needs are reflected in future planning, keeping the product direction synchronized with market demands.

Sprint Planning requires a clear understanding of the proposed work and its value. If items lack clarity, the Developers must collaborate with the Product Owner during the event to refine them, or adjust the scope. While Product Backlog refinement is ongoing, the team cannot plan effectively with ambiguous requirements, necessitating immediate real-time clarification.

The Sprint Review is designed for inspection and adaptation. When a stakeholder provides feedback revealing a mismatch between written requirements and real-world utility, the Scrum Team must embrace empiricism. The Product Owner creates new Product Backlog items to address the workflow gap, ensuring continuous alignment with customer needs.

The Scrum Master serves the team by protecting them from external interference, ensuring they remain focused on the Sprint Goal. By coaching stakeholders on the Scrum process and the importance of Sprint stability, the Scrum Master fosters a sustainable development environment. This action is critical because it prevents context switching, maintains team velocity, and upholds the integrity of the Scrum framework by enforcing the roles and boundaries defined in the Scrum Guide.

The Scrum Master acts as a servant-leader by removing organizational barriers and coaching the wider organization on Scrum principles. Helping the team visualize bottlenecks and engaging cross-functional stakeholders directly addresses systemic waste without taking away the team's ability to self-organize.

The Scrum Master serves the organization by helping it understand and apply empirical approaches. In a budgeting meeting, offering Sprint Review data and product metrics provides real evidence of progress and value, which can inform funding decisions better than detailed project plans. This approach respects the department heads' authority while gently guiding them toward more agile governance.

Coaching the organization toward self-organization requires active engagement with leadership to help them understand that Scrum shifts authority for how work gets done to the Scrum Team. True agility relies on intrinsic motivation and autonomy. By facilitating discussions and providing education on empirical process control, the ScrumMaster helps leadership transition from command-and-control to supportive servant leadership, ultimately building a healthier organizational ecosystem that enables Scrum Teams to deliver higher value safely and effectively.

Serving the Scrum Team means coaching self-management and empiricism, which includes clarifying that the Developers own and may adapt the Sprint Backlog and helping the team use the Retrospective to improve its way of working. Fixed roles, imposed velocity targets, and reporting rituals to the Scrum Master all substitute external control for the team's own accountability and would slow the growth the Scrum Master is trying to encourage.

The Developers are solely responsible for sizing and selecting work during Sprint Planning based on their capacity. If they realize an overcommitment, they must collaborate with the Product Owner to adjust the Sprint Backlog scope before the meeting ends. This protects team sustainability and ensures a realistic Sprint Goal can be achieved without compromising quality.

The Sprint Backlog is the plan for the Sprint and should not be changed in a way that endangers the Sprint Goal. The Scrum Master must coach the Product Owner on the impact of changing the plan during the Sprint. This ensures that the team maintains a stable environment to meet their commitments and protects the integrity of the Scrum process.

The Scrum Master serves the organization by leading, training, and coaching it in Scrum adoption, helping employees and stakeholders understand and enact empiricism for complex work, and removing barriers between stakeholders and Scrum Teams. Product direction, delivery excellence, and optional external coaching do not carry this accountability.

The Sprint Review exists so the Scrum Team and stakeholders can inspect the working Increment and adapt the Product Backlog together. A slide-driven event that omits the increment destroys the transparency stakeholders rely on. Coaching the Product Owner and Developers to rebuild the event around a live demonstration and collaborative discussion corrects the root cause.

Shortening the Sprint significantly increases the overhead of the Scrum events. The Scrum Master must ensure the team realizes that the events must be kept lean to fit within the new, tighter timebox. This is a critical competency because the Scrum Master needs to guide the team through the implications of process changes, ensuring they don't sacrifice the quality or the purpose of the events for the sake of speed.

The Scrum Master serves the Product Owner by coaching them on effective collaboration with the Developers. Helping the Product Owner establish a reliable cadence for clarifications ensures the Developers can maintain flow and deliver value. This approach addresses the root cause without undermining the Product Owner's authority or escalating prematurely.

The Scrum Master serves the Scrum Team by coaching on self-management and helping them improve their way of working. When coordination overhead increases, the Scrum Master should first help the team inspect and adapt their own practices, rather than imposing structural changes or adding management roles that conflict with Scrum principles.

The Scrum Master facilitates collaboration and coaches the Product Owner on empirical, value-driven techniques like backlog refinement rather than making the ordering decision for them. This empowers the Product Owner to own the backlog completely, maintaining their sole authority over prioritization while protecting the team from competing stakeholder demands.

The Scrum Master should coach the Product Owner on the value of the Sprint Goal and the negative impact of mid-Sprint priority changes. By helping the Product Owner understand that changes endangering the Sprint Goal should be deferred, the Scrum Master protects the team's focus while maintaining collaboration.

The Scrum Master serves the Product Owner by teaching effective Product Backlog management techniques and by facilitating stakeholder collaboration. Both actions build the Product Owner's capability and support informed ordering without taking over the Product Owner's accountability. Directing Developers or letting stakeholders vote would undermine the Product Owner's authority over the backlog.

The Scrum Master facilitates the protection of the Sprint Backlog by coaching stakeholders and the Product Owner on the impact of scope creep. By ensuring the team's capacity is respected, the Scrum Master fosters a sustainable development pace. This intervention is critical because the team's ability to achieve the Sprint Goal depends on maintaining focus and avoiding unnecessary distractions that undermine the integrity of the Sprint agreement.

The Scrum Master must make this discrepancy transparent to the organization, highlighting the risks of cumulative quality debt and compromised increments. By engaging leadership in a conversation about why the current definition is ignored, the Scrum Master helps uncover systemic barriers. This service is vital because an ignored Definition of Done means the organization is not actually delivering what it claims, leading to false confidence and hidden product risks that will inevitably surface later.

The Scrum Master facilitates the creation of a 'Definition of Done' by guiding the team, including the Product Owner, through a shared understanding of quality. The Product Owner provides the 'what' and 'why' from a market perspective, while the Developers define the technical constraints. By bringing these groups together, the Scrum Master ensures a common standard is established that protects the product's quality and ensures transparency for all stakeholders involved.

A Scrum Master focuses on the event's purpose: synchronizing activities and creating a plan for the next 24 hours. By enforcing the timebox and coaching the team on offline discussions, the Scrum Master helps the team maintain focus. These actions are essential for keeping the Daily Scrum efficient and ensuring the event serves as a planning opportunity rather than a status report or technical design session.

The Scrum Master serves the Scrum Team by coaching it in self-management and helping it improve its practices. When integration issues arise, the most appropriate action is to guide the Developers to enhance their Definition of Done and take ownership of their integration approach. This fosters continuous improvement and aligns with Scrum's empirical nature.

The Scrum Master is responsible for ensuring that the Sprint Planning event takes place and that the participants understand its purpose. They act as a facilitator, ensuring the team stays within the timebox and understands the goal. Their role is to coach the team on how to conduct the event effectively, ensuring the collaborative creation of the Sprint Backlog and clear definition of the Sprint Goal.

The Scrum Master must act as a facilitator and coach, helping the Product Owner understand how constant context switching degrades development flow and predictability. By coaching the Product Owner on sustainable backlog management and channelizing requests through the proper refinement process, the Scrum Master protects the team while preserving Product Owner autonomy.

Serving the Product Owner includes ensuring the backlog is healthy, prioritized, and transparent. By helping the Product Owner find the right ways to refine and manage the backlog, the Scrum Master ensures the team always has a clear view of the work ahead. These actions are fundamental to maintaining high levels of value delivery and ensuring that the product development process remains efficient and aligned with the organization's strategic objectives.

The Scrum Master coaches the organization on the purpose of the Sprint Review, which is collaboration and feedback on the product rather than just a demo. By ensuring that the session includes relevant stakeholders and fosters open dialogue, the Scrum Master helps the organization align their product roadmap with market realities. This service is critical because it turns a potentially passive presentation into an active, empirical event that drives future planning and product success.

The Scrum Master assists the organization in understanding the importance of an ordered, transparent, and refined Product Backlog. By coaching the Product Owner and stakeholders on these concepts, the Scrum Master ensures that the organization focuses on value and empirical feedback. This service is crucial because it ensures that the work being done aligns with organizational goals, prevents waste, and creates a clear, shared vision for the team and the business.

A self-managing team takes charge of their own work, fosters internal accountability, and adapts their processes to optimize their output. These characteristics signify that the team has moved away from needing external supervision and has achieved a level of maturity where they can deliver value independently, which is the ultimate goal of the Scrum framework for teams.

The Sprint Review is a collaborative working session in which the Scrum Team and stakeholders inspect the Increment and progress toward the Product Goal, then adapt the Product Backlog. It is not a formal approval gate, not a status presentation, and not an internal-only meeting. Its output is an updated Product Backlog that shapes what comes next.

Self-management grows when the Developers are told clearly that they own the Sprint Backlog and its execution, and when they are coached to organize around the Sprint Goal and choose how to distribute work. Explaining the Scrum Master's non-managerial role and letting the team decide together remove the dependency the team is demonstrating.

The Scrum Master serves the Product Owner by helping her effectively facilitate the Sprint Review and communicate progress toward the Product Goal. Coaching her to frame the event around the Product Goal, using the Increment and Product Backlog ordering as evidence, keeps her accountable while building her capability. Taking over, cancelling, or turning it into a technical demo all undermine the event's purpose and her ownership.

The Scrum Master should coach the team to focus on the value they can deliver in the Sprint rather than just a collection of tasks. By encouraging the team to look at the Product Backlog, the Scrum Master helps them find a coherent theme or outcome for the iteration. This is a core competency that helps the team transition from task-based work to outcome-based delivery.

The Developers must protect the Sprint Backlog from outside interference to ensure the Sprint Goal is met. Directing the stakeholder to the Product Owner maintains the integrity of the Scrum process. The Product Owner is the person responsible for the backlog and the value delivery, so they must assess any new requests against existing priorities and determine if they should be included in the product.

Velocity is a capacity measure intended solely for internal team planning, not a performance metric for comparison across teams. Publishing stack rankings based on velocity incentivizes gaming the system, inflates story points, and destroys psychological safety and collaboration. The ScrumMaster must coach leadership away from using internal metrics for evaluation, guiding them instead toward tracking value delivery, customer satisfaction, and business outcomes that reflect true organizational health.

Empirical process control relies on transparency, making historical velocity and backlog burndown charts ideal for forecasting. The Scrum Master helps the Product Owner utilize these transparent artifacts to manage stakeholder expectations realistically without resorting to speculative, rigid long-term project plans.

Scrum events are required for the Scrum Team to function, regardless of whether the Scrum Master is present. The team is self-managing and capable of facilitating their own meetings. While the Scrum Master helps ensure the events are productive, the team's commitment to the process should not depend on the presence of any one individual, reinforcing their independence and maturity.

The Scrum Master facilitates collaboration rather than imposing rules, helping the team inspect their current practices and build collective ownership over their quality standards. This empowers self-management and ensures the resulting Definition of Done genuinely reflects their technical capabilities and organizational constraints.

The Sprint Retrospective is the final event of the Sprint and exists to inspect how the team worked across individuals, interactions, processes, tools, and the Definition of Done. The team identifies the most impactful improvements and may add them to the next Sprint Backlog. Product inspection and backlog adaptation belong to the Sprint Review, while goal setting and item selection belong to Sprint Planning.

A newly formed Scrum Team often carries habits from functional hierarchies, so the Scrum Master serves it by coaching self-management and by helping the surrounding organization understand Scrum accountabilities. Together these actions shift decision-making about how to build the Increment to the Developers while reducing the pull of outside reporting expectations that fragment their focus.

The Scrum Master serves the organization by facilitating transparency regarding the impact of technical debt on velocity and quality. By encouraging the Product Owners and leadership to balance feature work with technical refinement, the Scrum Master helps the organization move toward sustainable development. This service is crucial because unchecked debt leads to slower delivery cycles and increased maintenance costs, ultimately hindering the organization's ability to respond to competitive market pressures over time.

The Developers are accountable for delivering high-quality, 'Done' work each Sprint. By managing their own progress and collaborating closely, they ensure that the Increment meets the team's definition of quality. These responsibilities are essential for the team to achieve its Sprint Goal and remain a self-managing unit that delivers consistent value to the customer.

The Scrum Master must act as a change agent and protector of the Scrum Team's integrity. By addressing this with organizational management, the Scrum Master highlights the negative impact of interrupted focus and broken team cohesion. This intervention is vital because it preserves the team's ability to self-organize and deliver on their commitments, ultimately preventing structural disruptions that lead to failed Sprints and lowered morale.

The Scrum Master supports the Product Owner by ensuring they understand how to manage the backlog effectively and by facilitating the necessary communication with stakeholders. These actions ensure that the backlog remains transparent, ordered, and aligned with the product's goals, which are foundational responsibilities for the Product Owner within the Scrum framework.

A Scrum Master serves the organization by ensuring that quality is built in, but also by preventing 'metric-driven' development that ignores the business context. While code coverage is a useful internal metric, mandating a universal, rigid target can lead to 'gaming' the metric. The Scrum Master must help the organization understand that value and quality are multifaceted, and teams should choose practices that maximize overall outcome.

The Scrum Master must lead by coaching and facilitating, not by dictating. These three actions empower the team to take ownership, learn from experience, and structure their work, which are foundational for self-management. By creating a safe environment and focusing on team-level reflection, the Scrum Master helps the team mature into a self-organizing unit that can handle complex work effectively without being micro-managed or directed by external leadership.

The Scrum Master serves the organization by helping it understand Scrum's theory, roles, and events. When teams are mislabeled and lack a Product Owner, the appropriate first step is education and coaching with leadership and teams, enabling incremental, transparent change rather than abrupt restructuring or silent noncompliance.

Removing impediments is a key responsibility that requires both immediate tactical support and long-term strategic influence. By identifying patterns, teaching others to solve their own problems, and involving management when necessary, the Scrum Master helps the organization improve its overall system of delivery. This work is essential because it turns the focus from merely 'doing' Scrum to truly 'being' agile, allowing the organization to operate more effectively and with less friction.

The Scrum Master should coach the Product Owner on effective Product Backlog management practices, including defining clear slicing strategies and ensuring items meet a shared definition of ready before Sprint Planning. This intervention directly improves the flow of value and ensures the team can inspect and adapt efficiently during execution.

Canceling a Sprint does not discard work. Completed Product Backlog items that satisfy the Definition of Done are reviewed and may be accepted by the Product Owner if potentially releasable, while incomplete items return to the Product Backlog for future consideration. The next Sprint still begins with Sprint Planning to establish a new Sprint Goal and Sprint Backlog.

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The timebox ensures the team focuses on creating a usable plan without over-investing in planning, while still allowing enough time to define the Sprint Goal and select the necessary Product Backlog items.

The Sprint Goal and Sprint plan are created together by the whole Scrum Team during Sprint Planning. No single accountability owns the scope; clarity comes from collaboration. Improving shared understanding of the Sprint Goal and selected items is a team responsibility, so the entire Scrum Team is the best answer to the described lack of clarity.

The Scrum Master protects the team from external interference and educates stakeholders on effective collaboration. By shifting stakeholder focus away from micromanagement and toward strategic empirical feedback, the Scrum Master preserves team morale and the integrity of the Sprint Review.

The Scrum Master serves the Product Owner by helping them find techniques for effective Product Backlog management and understanding the need for clear, concise items. This support is crucial because an effective Product Owner directly influences the team's ability to deliver value. By coaching the Product Owner, the Scrum Master ensures the entire Scrum Team operates efficiently towards the product's success.

The Daily Scrum is a 15-minute event for the Developers to synchronize and plan the next 24 hours. When it exceeds this time, the Scrum Master should coach the team on the event's purpose. By reminding them that it is a planning session rather than a problem-solving meeting, the Scrum Master helps restore the event's efficiency while respecting the team's self-management and autonomy.

The Sprint Retrospective is where the Scrum Team inspects itself and creates a plan for improvements it owns. When the event produces complaints but no action, the Scrum Master's accountability for the team's effectiveness calls for coaching on the event's purpose and helping the team take ownership of concrete improvements, not for taking over or replacing the event.