When a Product Owner raises concerns about the team’s commitment and productivity based on comparisons of velocity with other teams, this signals a need for coaching on empiricism, transparency, and appropriate use of Scrum metrics . As a Scrum Master, my response would focus on reframing the discussion from output comparison to value delivery and continuous improvement .

First, I would explain that velocity is a team-specific, contextual measure . Velocity reflects how much work a specific team completes within a given context, using its own Definition of Done, skills, tooling, and domain complexity. The Scrum Guide does not define velocity as a performance or comparison metric. Comparing velocity across teams is misleading and risks encouraging dysfunctional behavior, such as inflating estimates, cutting quality, or gaming the system. Therefore, a higher velocity does not automatically indicate higher productivity, commitment, or value delivery.

Second, I would explore the Product Owner’s underlying concern rather than focusing on velocity itself. Often, concerns about velocity are proxies for deeper issues such as:

Missed Sprint Goals,

Unmet stakeholder expectations,

Slow value delivery,

Quality problems or unpredictability.

As a Scrum Master, I would help the Product Owner articulate what outcome they are truly worried about , and then guide the discussion toward metrics and observations that better reflect those concerns, such as progress toward Product Goals, customer feedback, Increment quality, or predictability over time.

Third, I would reinforce the importance of empiricism and transparency . If there are genuine concerns about commitment or effectiveness, these should be inspected using transparent evidence within the team’s own context. The Sprint Review and Sprint Retrospective provide structured opportunities to inspect outcomes and ways of working. Rather than privately judging the team based on external comparisons, these concerns should be addressed openly and constructively with the Scrum Team.

Fourth, I would coach the Product Owner on Scrum Values , particularly Respect and Openness . Assuming lower commitment based on velocity comparisons risks undermining trust and psychological safety. Scrum encourages respecting the team as capable professionals and being open to learning what is actually limiting their effectiveness. Blame-oriented comparisons reduce the likelihood of honest inspection and improvement.

Finally, if improvement is needed, the Scrum Master should support the Scrum Team in identifying and addressing impediments . This may involve examining workload, technical debt, unclear backlog items, excessive dependencies, or organizational constraints. The focus should be on enabling the team to improve sustainably, not on pushing them to match another team’s numbers.

The Sprint Retrospective is a formal Scrum event where the Scrum Team inspects how the last Sprint went with respect to individuals, interactions, processes, tools, and their Definition of Done , and identifies improvements for future Sprints. The Scrum Master attends the Sprint Retrospective in multiple, complementary ways , consistent with the Scrum Guide.

First, the Scrum Master joins the Sprint Retrospective as a Scrum Team member . The Scrum Guide defines the Scrum Team as consisting of the Product Owner, Developers, and the Scrum Master. Therefore, the Scrum Master is not an external observer but a full participant in the event. As such, the Scrum Master actively inspects people, processes, and tools , and contributes insights based on their perspective and experience, while remaining respectful of the team’s self-management.

Second, the Scrum Master often facilitates the Sprint Retrospective . According to the Scrum Guide, the Scrum Master is accountable for ensuring that Scrum events take place and are productive. Facilitation may include helping the team create a safe environment, encouraging openness, ensuring balanced participation, keeping the discussion focused on improvement, and helping the team stay within the timebox. However, facilitation does not imply control; the Scrum Master facilitates to serve the team , not to direct outcomes.

Third, the Scrum Master supports empiricism during the Retrospective . By fostering transparency, encouraging honest inspection, and helping the team identify actionable improvements, the Scrum Master strengthens the Scrum pillars of transparency, inspection, and adaptation . The Scrum Master may also help the team turn improvement ideas into concrete actions that can be planned for the next Sprint.

Finally, the Scrum Master helps ensure that the Sprint Retrospective results in meaningful adaptation . While the Scrum Team decides what improvements to implement, the Scrum Master supports the team in identifying impediments, coaching on improvement techniques, and helping remove organizational or systemic obstacles that are beyond the team’s direct control.

In summary, the Scrum Master attends the Sprint Retrospective by joining as a full Scrum Team member , participating in inspection , often facilitating the event , and supporting continuous improvement and empiricism . This balanced participation ensures that the Retrospective remains a powerful mechanism for learning and adaptation rather than a ritualistic meeting.

A Development Team claiming self-organization as a reason to stop the Daily Scrum reflects a misunderstanding of both self-management and the purpose of Scrum events. As a Scrum Master, I would address this through teaching, coaching, and empiricism rather than enforcement.

Daily Scrum Is Mandatory in Scrum

First, it must be made clear that the Daily Scrum is a required Scrum event . The Scrum Guide defines it as a 15-minute event held every working day of the Sprint for the Developers. Choosing to eliminate it means the team is no longer practicing Scrum , regardless of how well they collaborate informally.

Self-Organization Does Not Mean Skipping Empiricism

Self-organizing (self-managing) teams decide how to do the work, not whether to inspect and adapt. Scrum events exist to uphold empirical process control . The Daily Scrum specifically enables:

Transparency about progress toward the Sprint Goal,

Inspection of the Sprint Backlog and current plan,

Adaptation of work for the next 24 hours.

Informal collaboration throughout the day does not replace the shared, intentional inspection moment that the Daily Scrum provides.

The Daily Scrum Is Not a Ritual or Status Meeting

If the Daily Scrum feels like a needless ritual, this is a signal that it is not being used correctly . It should not be a status report or a meeting for the Scrum Master or Product Owner. Instead, it is a planning event for the Developers , focused on how to best achieve the Sprint Goal.

As a Scrum Master, I would coach the team to improve the Daily Scrum , for example by:

Centering the discussion on progress toward the Sprint Goal,

Making impediments and risks explicit,

Using different formats that suit the team’s context.

Risks of Removing the Daily Scrum

Removing the Daily Scrum reduces transparency and delays inspection and adaptation. Problems such as integration issues, misalignment, or threats to the Sprint Goal may surface too late, increasing risk and waste. Over time, this undermines predictability and value delivery.

Scrum is fundamentally based on Empiricism , also referred to as Empirical Process Control . This means that Scrum recognizes that complex work, such as software development, cannot be fully understood or predicted upfront. Instead, decisions are made based on experience, observation, and evidence , forming a continuous closed feedback loop .

Empirical Process Control rests on three pillars: Transparency, Inspection, and Adaptation . Scrum provides a structured framework of roles, events, and artifacts that explicitly support and reinforce each of these pillars.

Transparency

Transparency ensures that all significant aspects of the process and product are visible to those responsible for the outcome. In Scrum, transparency is created through clearly defined artifacts such as the Product Backlog, Sprint Backlog, and Product Increment , each governed by a shared Definition of Done. Scrum Events further enhance transparency by creating regular opportunities to share progress, challenges, and current state. Without transparency, inspection would be misleading and ineffective.

Inspection

Scrum prescribes frequent and regular inspection of both the product and the process. Each Scrum Event serves as an inspection point:

The Daily Scrum inspects progress toward the Sprint Goal,

The Sprint Review inspects the Increment and adapts the Product Backlog,

The Sprint Retrospective inspects the team’s ways of working.

These inspections are intentionally timeboxed and lightweight to avoid excessive overhead while still enabling timely feedback.

Adaptation

Inspection is meaningful only if it leads to adaptation . Scrum explicitly enables adaptation by allowing changes to plans, processes, and backlog content based on what is learned. The Sprint Backlog may be adapted during the Sprint, the Product Backlog is adapted after the Sprint Review, and team practices are adapted following the Sprint Retrospective.

Closed Feedback Loop

Together, transparency, inspection, and adaptation form a closed feedback loop . Scrum’s short iterations (Sprints) ensure that learning occurs frequently, enabling the Scrum Team and stakeholders to respond quickly to change, reduce risk, and improve outcomes over time.

If not all Development Team members are present at the Daily Scrum , several risks are introduced that undermine empiricism , collaboration, and the team’s ability to achieve the Sprint Goal .

First, transparency is reduced . The Daily Scrum exists to create a shared understanding of progress, plans, and impediments. When some Developers are absent, their work, discoveries, risks, or impediments are not fully visible to the rest of the team. This results in an incomplete or inaccurate picture of the Sprint Backlog’s current state.

Second, inspection becomes ineffective . The Daily Scrum is the primary event where Developers inspect progress toward the Sprint Goal. Missing perspectives means that inspection is based on partial information, increasing the likelihood that important issues—such as integration problems, dependencies, or quality concerns—go unnoticed until later in the Sprint.

Third, adaptation is delayed or suboptimal . Without full participation, the team may make planning adjustments that do not account for all constraints or opportunities. This can lead to rework, misalignment, or duplicated effort, and increases the risk of failing to meet the Sprint Goal.

Fourth, the absence of team members weakens collective ownership and accountability . The Daily Scrum reinforces that the Developers are jointly responsible for the Sprint Goal. Regular absence can create silos, reduce collaboration, and signal that shared planning and alignment are optional.

Finally, over time, inconsistent attendance can turn the Daily Scrum into a status meeting for those present , rather than a collaborative planning event for the whole team. This undermines Scrum Values, particularly Commitment, Respect, and Openness .

This situation represents a breakdown in Product Backlog transparency and collaboration , which directly threatens empiricism and value delivery. As a Scrum Master, my responsibility is not to solve the problem myself, but to enable the Scrum Team and the organization to resolve it .

1. Reframe the Problem: Requirements vs. Product Backlog

First, I would help both parties reframe the issue. In Scrum, we do not work with “requirements” in a traditional, fixed sense. Instead, we work with a Product Backlog that is emergent, ordered, and continuously refined . Lack of clarity in Product Backlog Items means that the backlog is not in a usable state, which is an impediment to the Developers.

2. Make the Impact Transparent

Next, I would facilitate a conversation to make the impact of unclear backlog items transparent :

Developers cannot reliably forecast work,

Sprint Goals are put at risk,

Rework and waste increase,

Delivery of value slows down.

This conversation should involve the Product Owner and be grounded in evidence , not blame. The goal is shared understanding of the consequences, not assigning fault.

3. Reinforce Product Owner Accountability

The Scrum Guide is clear that the Product Owner is accountable for maximizing value and for Product Backlog management , which includes ensuring that Product Backlog Items are clear, understood, and ordered. Being “too busy” does not remove this accountability. As a Scrum Master, I would coach the Product Owner to recognize that insufficient availability is itself an organizational impediment.

4. Enable Collaboration, Not Handoffs

At the same time, I would coach the Developers that clarity is often co-created , not simply provided. Scrum encourages close collaboration between Developers and the Product Owner. Techniques such as:

Regular Product Backlog refinement,

Joint discussions during Sprint Planning,

Asking focused questions around the Sprint Goal, can significantly improve shared understanding without relying on detailed upfront specifications.

5. Address Organizational Constraints

If the Product Owner’s lack of availability is due to organizational overload or competing responsibilities, this becomes a systemic impediment . In that case, the Scrum Master must raise this issue to the organization and help leadership understand that a Product Owner who is not sufficiently available puts product outcomes at risk.

A distant Product Owner represents a risk to value delivery, transparency, and empiricism . While the Product Owner has provided a Product Backlog for the Sprint, lack of collaboration during the Sprint undermines learning and informed decision-making. As a Scrum Master, the focus should be on coaching, enabling collaboration, and addressing systemic impediments , not substituting for the Product Owner.

1. Make the Impact Transparent

The Scrum Master should help make the impact of the Product Owner’s absence visible :

Reduced ability to clarify Product Backlog Items,

Slower decision-making when discoveries occur,

Increased risk to the Sprint Goal and product value.

This transparency should be established through respectful conversations with the Product Owner and, if needed, through Scrum events such as the Sprint Retrospective.

2. Coach the Product Owner on Accountability

The Scrum Guide states that the Product Owner is accountable for maximizing value and Product Backlog management , which requires ongoing collaboration with Developers. The Scrum Master should coach the Product Owner to understand that handing over a backlog at Sprint Planning is not sufficient and that availability during the Sprint is essential for empiricism.

3. Enable Better Collaboration Without Replacing the Product Owner

The Scrum Master should help create opportunities for collaboration, such as:

Encouraging regular clarification moments during the Sprint,

Improving Product Backlog refinement so fewer questions remain unanswered,

Helping Developers prepare focused questions to use limited Product Owner availability effectively.

However, the Scrum Master must not take over Product Owner responsibilities , as this would blur accountabilities.

4. Address Organizational Causes

If the Product Owner’s distance is due to workload, role confusion, or organizational pressure, this becomes an organizational impediment . The Scrum Master should raise this issue with leadership and help the organization understand the risk of an unavailable Product Owner to product outcomes.

The situation described directly touches on several core Scrum Values , which guide behavior and collaboration within Scrum Teams. In particular, the values of Courage, Respect, and Openness are most prominently involved.

First, the value of Courage is demonstrated by the junior developer. Speaking up about feeling unheard, especially in front of more experienced colleagues, requires personal courage. Scrum encourages team members to be brave in raising difficult or uncomfortable issues so that problems can be addressed rather than ignored. Without courage, important impediments to collaboration and effectiveness would remain hidden.

Second, the situation highlights a lack of Respect in team interactions. Scrum emphasizes that Scrum Team members respect each other as capable, independent individuals. Interrupting a colleague or disregarding their input—regardless of seniority—undermines this value. Respect is essential for effective collaboration and for creating an environment where all team members can contribute fully.

Third, the value of Openness is central to this scenario. Scrum Teams are expected to be open about challenges, feedback, and differing perspectives. Openness also means being receptive to ideas from all team members, independent of role, experience level, or background. Disregarding input from a junior developer contradicts Scrum’s emphasis on openness and reduces the quality of decision-making.

When the Product Owner becomes unexpectedly unavailable, the Scrum Team must respond in a way that preserves continuity, transparency, and value delivery , while respecting Scrum accountabilities.

Short-Term Response

In the short term , covering the current Sprint and possibly the next Sprint, the Scrum Team should be able to continue working. Scrum is designed to be resilient to short-term disruptions. The team can proceed by relying on:

The Product Vision previously communicated by the Product Owner,

The current state and ordering of the Product Backlog , which should already reflect the Product Owner’s value decisions.

During this period, the Developers continue to work toward the Sprint Goal, and the Scrum Master ensures that Scrum events take place and remain productive. No one should assume the Product Owner role informally, as this would undermine accountability.

Longer-Term Impact

If the Product Owner’s absence extends beyond a short period, it becomes an impediment to the Scrum Team. The Product Owner is accountable for maximizing product value and managing the Product Backlog. Prolonged absence prevents effective backlog ordering, stakeholder collaboration, and value-based decision-making.

In this case, the Scrum Master must make the impediment visible to the organization . This includes explaining the impact on value delivery and helping leadership understand the need for a clear Product Owner accountability. The organization should then appoint a new Product Owner to ensure continuity of decision-making and accountability.

If team members see no value in defining a Sprint Goal, this indicates a fundamental misunderstanding of Scrum. As a Scrum Master, I would explain to my fellow Scrum Master that the Sprint Goal is a core element of Scrum and is essential for alignment, commitment, and empiricism.

First, the Sprint Goal explains why the Scrum Team is doing the work in the Sprint . According to the Scrum Guide, the Sprint Goal is the single objective for the Sprint and provides coherence to the Sprint Backlog. Without a clear “why,” Sprint work becomes a collection of unrelated tasks rather than a purposeful effort to deliver value. The Sprint Goal helps the team understand the intent behind the selected Product Backlog Items and aligns daily decisions with that intent.

Second, the Sprint Goal represents a commitment by the Scrum Team . The team commits to doing everything in its power to achieve the Sprint Goal, even though the specific scope may evolve. This commitment fosters focus and shared accountability. Instead of optimizing for individual tasks, the team optimizes for achieving the Sprint Goal as a whole.

Third, the Sprint Goal actually creates flexibility rather than restricting it . When new discoveries, risks, or opportunities emerge during the Sprint, the team can adapt the Sprint Backlog as long as those changes do not endanger the Sprint Goal. This allows the team to respond to change while maintaining stability of purpose. Without a Sprint Goal, change becomes arbitrary and increases the risk of losing focus.

Fourth, the Sprint Goal enables effective inspection and adaptation . During the Daily Scrum, the team inspects progress toward the Sprint Goal and adapts their plan accordingly. Similarly, at the Sprint Review, stakeholders can inspect whether the Sprint Goal was met. Without a Sprint Goal, there is no meaningful benchmark for inspection.

Finally, it is important to be clear that without a Sprint Goal, Scrum is not being practiced as intended . The Sprint Goal is a required element of Scrum, and removing it undermines transparency and weakens the empirical foundation of the framework.