Certified ScrumMaster (CSM) — Questions 76–150

Scrum relies on transparency and realistic forecasting to establish a sustainable cadence. The Development Team must collaborate immediately with the Product Owner to right-size the Sprint Backlog before finalizing the plan. This ensures the team commits only to work they can realistically complete, maintaining predictability and avoiding burnout.

The Scrum Master serves the organization by helping it understand how Scrum interacts with existing policies. Individual performance rankings based on output metrics conflict with Scrum's emphasis on self-managing teams and collective accountability. The most effective action is to coach HR and leadership on the unintended consequences of such metrics and to collaborate on alternatives that reflect team-level value delivery.

The Scrum Master serves the Product Owner by coaching him to order the Product Backlog effectively. Helping him learn value-based techniques such as cost of delay, risk assessment, and stakeholder impact, and encouraging a transparent rationale, addresses the root cause of loudest-voice ordering. Bypassing his authority, outsourcing prioritization, or using arbitrary ordering all fail to build his capability and undermine Scrum accountabilities.

Self-managing means the team decides who does what, when, and how. This represents a shift from traditional command-and-control management to a model where the team members take collective responsibility for their work. This is essential for Scrum because it empowers those closest to the work to make the best technical decisions, leading to faster innovation and higher quality outcomes.

The Developers are self-managing and own the Sprint Backlog, so they decide how to build the Increment. Adopting a simplifying library is an implementation choice within their authority, as long as the Sprint Goal and Definition of Done remain intact. No Product Owner approval or Scrum Master ruling is required for such a technical decision.

The Scrum Master should facilitate a retrospective to analyze the cause of the unfinished work. High WIP limits often indicate a lack of focus or poor refinement. By guiding the team to visualize their flow, the Scrum Master helps them identify bottlenecks and understand how limiting work in progress improves cycle time and the ability to achieve the Sprint Goal consistently.

The Scrum Master acts as a facilitator during planning to ensure the team converges on a common objective. By helping the team focus on the value they aim to deliver rather than just a list of tasks, the Scrum Master guides them toward a coherent Sprint Goal. This is critical for team alignment, as a shared goal is the foundation for effective self-management and focus throughout the remainder of the Sprint.

The Scrum Master should coach the Developers to take ownership of the Daily Scrum and the Sprint Backlog. The Daily Scrum exists for the Developers to inspect progress toward the Sprint Goal and adapt their plan. When the Scrum Master runs the event and assigns tasks, the team is not self-managing, even if they deliver.

These policies reflect a traditional project management mindset that conflicts with Scrum's empirical process. A Scrum Master serves the organization by leading the transformation, identifying how existing policies hinder agility. By engaging with leadership to modify these constraints, the Scrum Master enables the team to focus on value delivery rather than compliance with bureaucratic processes that provide little to no agility benefits.

The Scrum Master's role is to facilitate the removal of blockers, especially those requiring external influence. Escalating to management is a last resort, as the Scrum Master should first try to resolve the dependency through direct communication between teams. By actively working to clear the path, the Scrum Master protects the team from organizational friction, allowing them to focus on delivering value without getting bogged down in external bureaucratic delays.

The Scrum Master must facilitate a conversation with the Product Owner about the impact of their absence on the team's ability to deliver. If the issue persists, the Scrum Master should escalate the impediment to management, as a non-engaged Product Owner is a critical blocker to the success of the Scrum Team and the product's value delivery.

The Scrum Master must protect the team from external interference that disrupts the Scrum process. This situation is a classic case of lack of organizational support for the Scrum structure. By coaching the organization and the Developer, the Scrum Master helps align stakeholders on the benefits of the team's focus and the importance of the Sprint Goal over individual, siloed tasks.

The Scrum Master must act as a coach to the entire organization, helping them understand that Scrum Teams are self-managing units. By facilitating a conversation about autonomy and the benefits of empirical process control, the Scrum Master helps the manager transition to a supportive role. This is critical for the team to mature, as persistent reliance on external permission prevents true agility and innovation.

Servant-leadership focuses on the needs of the team and the organization, prioritizing growth and removing impediments. An effective Scrum Master does not command but enables. These traits foster trust, improve team autonomy, and create an environment where high-performing, self-organizing teams can thrive by focusing on continuous improvement and the delivery of value rather than adhering to rigid, top-down control structures.

The Scrum Master facilitates an environment of psychological safety and collaboration. By coaching the team on self-organization, the Scrum Master empowers members to resolve technical disagreements directly rather than acting as a proxy. This builds team maturity, aligns with servant leadership principles, and fosters collective ownership over architecture and implementation details without creating dependency on the Scrum Master.

The Daily Scrum is a 15-minute event for inspection of progress toward the Sprint Goal and adaptation of the Sprint Backlog. When technical issues arise, the Scrum Master should coach the team to identify these as topics for separate, focused discussions after the Daily Scrum. This ensures the event remains efficient and focused on planning, while keeping the team's collaboration centered on achieving the shared outcome within the designated timebox.

The Scrum Master serves the Product Owner by fostering an environment where the 'why'—the product vision and value—is clearly communicated. By coaching the Product Owner to share the intent behind their decisions, the Scrum Master ensures the Developers are motivated and empowered to build the right solutions. This alignment prevents the team from becoming just a feature factory and helps them contribute their expertise to the product's success.

Self-management is the foundation of Scrum, and the Scrum Master encourages this by stepping back from directing activities. By creating a space where the team owns their decisions and outcomes, the Scrum Master fosters maturity and accountability. This is critical because a team that cannot manage its own work will always remain dependent on external instruction, which is the antithesis of the agility that Scrum promotes.

Coaching the Product Owner on the Sprint Goal's purpose and the effects of mid-Sprint changes directly serves their need to understand Scrum's boundaries. It empowers the Product Owner to manage stakeholder feedback without destabilizing the Developers, preserving focus and value delivery.

The Scrum Master serves the wider organization by removing organizational impediments that hinder team progress. By engaging stakeholders and helping visualize systemic bottlenecks across value streams, the Scrum Master protects the team's focus and drives structural improvements. This ensures sustainable flow and prevents burnout caused by external operational dependencies outside the direct control of the developers.

The Scrum Master serves the Product Owner by coaching on Product Backlog ordering techniques and facilitating collaboration with stakeholders. These actions help the Product Owner maximize value and ensure the backlog reflects stakeholder needs. They build the Product Owner's capability without taking over their responsibilities.

The Scrum Master serves the Scrum Team by coaching it to create a Definition of Done, which provides the shared standard for a complete and potentially releasable Increment. Establishing it now, rather than deferring, preserves transparency and supports empirical inspection. The team owns this commitment, so the Scrum Master facilitates its creation rather than imposing or delaying it.

The Scrum Master must protect the team from metrics that encourage unhealthy behavior. Individual performance tracking is antithetical to the collaborative nature of Scrum. By educating HR on the focus on 'Done' increments and team-level outcomes, the Scrum Master helps the organization shift toward measuring value delivered rather than activity performed, which is critical for fostering a true agile environment.

Annual fixed-scope budgeting creates a waterfall-like constraint that undermines Scrum's empirical approach of iterative value delivery. The ScrumMaster must engage financial stakeholders to introduce agile budgeting concepts, such as funding persistent value streams or products rather than fixed projects. This cultural and financial shift allows the organization to pivot based on feedback, reduces upfront risk, and aligns budgeting practices with true business agility and continuous value realization.

The Product Owner is solely responsible for maximizing product value and managing the Product Backlog. Their decisions regarding ordering reflect stakeholder input, market analysis, and strategic vision. This matters because a single decision-maker prevents conflicting priorities from paralyzing the Development Team during sprint execution and planning.

The Scrum Master serves the Product Owner by helping with Product Goal definition and Product Backlog management techniques, and by facilitating stakeholder collaboration as needed. These actions directly address the Product Owner's time drain and enable more focus on value and Developer collaboration, without overstepping accountabilities.

The Scrum Master serves the Product Owner by helping them use empirical data and facilitating collaboration with the Developers to create forecasts. Teaching the use of velocity and burn-down charts, and facilitating estimation workshops, empower the Product Owner to make informed forecasts. These actions align with Scrum's empirical nature and respect the Product Owner's accountability for stakeholder communication.

The Scrum Master serves the Scrum Team by facilitating self-organization and helping them resolve internal conflicts rather than imposing external rules. Encouraging the developers to collaborate on updating their Definition of Done or team agreements fosters ownership. This approach builds team maturity and sustainable engineering practices while preventing reliance on the Scrum Master as a mediator.

The Sprint Backlog belongs to the Developers and is expected to change as they learn more during the Sprint. Because the Sprint Goal stays viable, the Developers can revise their plan without permission from the Product Owner or Scrum Master. Re-planning via a new Sprint Planning event or canceling the Sprint is unnecessary and not supported by Scrum.

The Daily Scrum is an internal inspection and adaptation event solely for the Development Team to plan their next 24 hours. Allowing external stakeholders to hijack the event turns it into a status-reporting meeting, destroying its core purpose and psychological safety for the practitioners.

The Scrum Master must make the impact of this disruption transparent and facilitate a discussion with leadership regarding organizational priorities. By highlighting the cost of multi-tasking and broken flow, the Scrum Master educates the organization on the systemic consequences of shifting resources. This service is essential for protecting the team's ability to deliver a Done increment and encourages the organization to move toward a model where teams have the necessary, stable capacity to succeed.

The Sprint Review is a collaborative working session where the Scrum Team and stakeholders inspect the outcome of the Sprint and discuss future adaptations. While the timebox of up to 4 hours for a 1-month sprint is correct and the attendee list is fully compliant, treating the event merely as a one-way demonstration rather than a collaborative working session violates its spirit.

The Scrum Master facilitates the conversation to ensure the team aligns on the value they intend to deliver. A clear Sprint Goal provides focus and direction. Without it, the team is just a group of individuals working on tasks, rather than a cohesive unit working towards a shared outcome, which is essential for maximizing the value delivered during the Sprint.

The Scrum Master serves the Product Owner by helping them understand and apply Scrum practices. When a Product Owner frequently changes the Sprint Goal, the Scrum Master should first seek to understand the underlying reasons and then coach them on the purpose of the Sprint Goal and the negative impact of mid-Sprint changes on focus and value delivery. This approach respects the Product Owner's role while promoting Scrum principles.

The Scrum Master must protect the Scrum Team's empirical process and focus on value delivery rather than vanity metrics. By educating the manager on why utilization-based tracking undermines self-organization and team-based performance, the Scrum Master prevents the implementation of practices that conflict with Scrum. This is essential for maintaining an environment where team autonomy and focus on outcome-based delivery remain the primary drivers of organizational success.

The Scrum Master should facilitate a plan for the team to build cross-functional skills. By identifying the risk early, the team can begin to pair-program or cross-train, reducing the dependency. This is a core competency, as the Scrum Master's goal is to help the team become self-managing and resilient, ensuring that one individual's absence does not stop the entire team's delivery progress during a Sprint.

The Sprint Review is a working session for inspecting the Increment and adapting the Product Backlog. New requests should be directed to the Product Owner for consideration in future Sprints. The Scrum Master should facilitate this understanding and protect the Developers from mid-Sprint disruptions, ensuring the Sprint Goal remains intact.

The Scrum Master serves the Product Owner by ensuring they understand how to arrange the Product Backlog to maximize value. When business goals are absent, the Scrum Master should facilitate discussions to define a clear Product Goal. This provides the necessary framework for the Product Owner to make informed decisions about priority, ensuring the work aligns with the overall product vision and organizational objectives.

The Scrum Master must protect the integrity of the Scrum framework by clarifying that the Development Team alone estimates and pulls work. Product Owners manage value, not capacity. This distinction matters because forcing arbitrary commitments destroys morale and distorts forecasting metrics.

The Scrum Master serves the Scrum Team by coaching it in self-management and helping it become cross-functional and accountable for its own work. When Developers wait for direction on task assignment and rely on the Scrum Master for every impediment, the appropriate response is to build their capability to decide and act themselves. Shifting decisions to the Product Owner or escalating for an external owner relocates authority instead of growing the team.

The Scrum Master must clarify that the Product Owner is the only one accountable for backlog management. Taking on this task would violate Scrum accountabilities and create a dependency that harms the team's long-term health. The Scrum Master's role is to coach the Product Owner on how to manage their time better and explain to the team why the Product Owner is the only one who can fill this role.

Serving the Product Owner includes ensuring that stakeholders are engaged and that the Product Owner is effectively managing their expectations. These actions foster transparency and ensure that the product direction remains aligned with organizational goals. By actively facilitating these interactions, the Scrum Master ensures the Product Owner has the necessary information to make informed decisions about product priority and future value, thereby enhancing the overall success of the product.

The Daily Scrum is a 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. When the team views it as a status report, the Scrum Master should coach them on its purpose and help them self-manage the event, thereby restoring its value and aligning with Scrum theory.

Managing feedback is essential for maintaining a focused and effective Product Backlog. By helping the Product Owner categorize, prioritize, and integrate feedback into their existing processes, the Scrum Master ensures that the feedback leads to actual improvement rather than chaos. These strategies keep the Product Owner in control of the product's direction while ensuring stakeholder transparency.

A Scrum Master serves the organization by fostering an environment conducive to Scrum. This involves both internal coaching and external advocacy. By focusing on systemic improvements and cultural alignment, the Scrum Master ensures that Scrum is implemented effectively and sustainably across all levels of the business, rather than just within the isolated boundaries of individual Scrum Teams.

The Scrum Master serves the team by facilitating a deeper investigation into the root cause of the drop in velocity during the Retrospective. Rather than focusing solely on the metrics, the Scrum Master encourages transparency and inspection of team dynamics, process blockers, or environmental issues. Addressing these systemic impediments allows the team to self-organize and implement improvements, ensuring the team remains resilient and capable of delivering consistent value in future Sprints.

The Scrum Master supports the Product Owner by coaching them on effective Product Backlog management and ensuring the team understands the need for clear, concise items. This service improves the flow of value and ensures the team is always working on the most important tasks. By facilitating effective communication between the PO and the team, the Scrum Master ensures alignment on the product vision and individual Sprint goals.

The Scrum Master serves the Product Owner by coaching them on how backlog ordering affects the Developers' focus and Sprint Goal. Encouraging collaboration with the Developers helps the Product Owner make better decisions without undermining their authority. This approach fosters understanding and self-management, aligning with Scrum values.

The Scrum Master serves the Product Owner by coaching them on techniques for Product Backlog management and product value maximization. By demonstrating how refinement drives empirical learning and release readiness, the Scrum Master helps transform a perceived chore into a powerful strategic advantage for the entire team.

The Scrum Master is an agent of change, responsible for the adoption of Scrum. This requires deep organizational knowledge and the ability to influence processes at scale. By focusing on education, process improvement, and structural change, the Scrum Master helps the organization move from traditional, siloed thinking toward a more agile, value-driven culture that supports the effectiveness of their Scrum Teams.

The Scrum Master can introduce various techniques for backlog refinement, such as user story mapping or INVEST criteria. By providing these tools, the Scrum Master empowers the Product Owner to improve the backlog, ensuring that items are ready for the Developers. This competency is essential for maintaining a healthy workflow, as smaller, well-refined items are easier for the team to estimate, plan, and deliver within a Sprint.

The Product Owner is the sole person responsible for managing the Product Backlog. This includes clearly expressing items, ordering them, and ensuring the backlog is transparent, visible, and understood. This accountability is vital because it creates a single source of truth for what the team should build next, preventing confusion and ensuring the team always works on the highest-value items first.

The Scrum Master facilitates the Retrospective to ensure it is positive, productive, and focused on improvement. They do not own the improvements; the team does. By facilitating the meeting, the Scrum Master helps the team inspect their process and identify ways to become more effective in the next Sprint, which is the primary goal of the Retrospective event in Scrum.

The Scrum Master serves the Scrum Team by coaching self-management and fostering collaboration. Coaching the Developers on frequent integration and facilitating a Retrospective where they choose how to work together more closely builds ownership. Mandatory meetings, forced reassignments, or backlog prescriptions impose solutions from outside the Developers, which weakens the self-management the Scrum Master is meant to strengthen.

The Daily Scrum is for the Developers to plan their work for the next 24 hours. While the Product Owner is welcome, their presence is not required unless they have items on the Sprint Backlog they are actively working on. The Scrum Master should ensure the Developers had the autonomy and information they needed to complete their synchronization effectively without the Product Owner, keeping the event focused on its primary purpose of developer alignment.

The Scrum Master serves the Product Owner by helping them articulate the product vision and the value of specific items. By facilitating sessions where the Product Owner explains the context and the desired outcome to the Developers, the Scrum Master ensures that the team understands the 'why', leading to better solutions and higher engagement from the team.

The Scrum Master should coach the Developers on healthy conflict resolution and facilitate a conversation, as well as raise the issue in the Sprint Retrospective for team-wide improvement. These actions serve the team by building conflict resolution skills and leveraging the Retrospective for collective adaptation. They empower the team to self-manage and improve communication, rather than relying on the Scrum Master to solve the problem or avoiding it.

The Scrum Master serves the Scrum Team by facilitating collaboration and helping members resolve conflicts. Facilitating a conversation allows the Developers and Product Owner to understand each other's concerns and jointly decide on an approach that balances feature delivery with technical health. This respects the Product Owner's accountability for value and the Developers' need for sustainable pace.

The correct action is to coach the Developers on the purpose of the Daily Scrum and help them refocus on the Sprint Goal. The Scrum Master serves the Scrum Team by fostering self-management and helping the team improve its practices. By guiding the Developers to coordinate with each other rather than report status, the Scrum Master enables the team to take ownership of the event and its outcomes, which is central to the Scrum Master's role.

Trust is built through transparency and the successful delivery of value. By fostering an environment where failures can be discussed openly and successes are celebrated, the Scrum Master helps the team build psychological safety. This is fundamental for high-performing teams, as it allows for honest communication and risk-taking, both of which are required to innovate and improve consistently over time within the Scrum framework.

The Scrum Master must protect the team from external interference and maintain the Product Backlog's transparency. By coaching the CTO on the Scrum framework, the Scrum Master ensures that all work flows through the proper channels. This is crucial for maintaining the team's focus and the integrity of the product, as 'hidden' features undermine the Product Owner's ability to prioritize effectively and manage stakeholder expectations.

Facilitating a focused, timeboxed workshop with clear objectives directly serves the Product Owner by enabling efficient stakeholder collaboration and alignment on the Product Goal. This approach reduces endless debate and helps the Product Owner validate direction without abdicating accountability.

The Sprint Review is a working session designed to inspect the Increment and adapt the Product Backlog based on stakeholder feedback. Discontent from stakeholders indicates a shift in understanding or requirements, which the Product Owner must capture and incorporate into the Product Backlog as new items. This feedback loop validates the empirical nature of Scrum, ensuring the product evolves to meet real market needs.

The Scrum Master should facilitate a discussion between the Product Owner and the Developers. It is possible there is a misunderstanding of the backlog order or the value of the items. By ensuring transparency and open communication, the Scrum Master helps the team realign their efforts with the Product Owner's strategic vision and the agreed-upon priorities.

The Scrum Master must clarify the accountabilities of the Product Owner, emphasizing their focus on maximizing value and product success. By educating leadership, the Scrum Master helps ensure the Product Owner is given the authority and support needed to make effective decisions. This service is vital because a misunderstood role leads to conflicting expectations and poor product outcomes, ultimately undermining the entire Scrum effort within the organization.

The Scrum Master serves the organization by facilitating an environment where the Product Owner can succeed. This involves helping the Product Owner communicate effectively with stakeholders and ensuring the backlog reflects a clear, value-based strategy. By teaching stakeholders about the empirical nature of the product lifecycle, the Scrum Master reduces the pressure on the Product Owner, allowing them to focus on maximizing product value.

The Scrum Master serves the Product Owner by helping them manage stakeholder engagement effectively. Coaching on techniques such as setting boundaries, scheduling dedicated time, or delegating can empower the Product Owner to balance stakeholder needs with Product Backlog refinement. This approach respects the Product Owner's accountability while fostering a productive environment.

The Scrum Master serves the Product Owner by coaching on effective Product Backlog management and communication. Helping the Product Owner articulate value directly addresses the struggle and strengthens collaboration with Developers, while keeping product accountability where it belongs.

The Scrum Master must facilitate a conversation to uncover the root cause of the failure. By observing the team and encouraging them to inspect their process, the Scrum Master helps them identify systemic issues. This is a crucial diagnostic step that respects team autonomy while fulfilling the Scrum Master's duty to improve the team's effectiveness and agility through empirical process control.

The Scrum Master must protect the team from metrics that discourage collaboration and promote individual competition. Annual bonuses based on individual performance are a legacy management practice that conflicts with the team-based approach of Scrum. The Scrum Master's role is to educate the manager on why this policy is detrimental and suggest alternative, team-based metrics that better align with the organization's agile goals.