Dealing with an Unavailable Product Owner

An unavailable Product Owner is a problem for a Scrum Team. Their role, as defined by the Scrum Guide, is to maximize the value of the product resulting from the work of the Scrum Team. This requires constant engagement with stakeholders, the market, and the Developers. When a Product Owner is consistently absent, unresponsive, or simply too busy, the team's ability to deliver value is severely hampered. This isn't just an inconvenience; it's a fundamental breakdown in the Scrum framework, leading to stagnation, misdirection, and frustration for everyone involved.

Recognizing the Symptoms

The first step is to recognize the signs of an unavailable Product Owner. This isn't always obvious. Sometimes, the Product Owner is technically present but not engaged. Other times, they are genuinely overloaded. Common symptoms include a stagnant Product Backlog, frequent questions from Developers going unanswered, and a lack of clear direction on what to build next. The team might find themselves pulling work from a poorly refined backlog, making assumptions, or even reinventing the wheel.

Consider these indicators:

• Product Backlog Refinement sessions are cancelled or poorly attended by the Product Owner.
• Developers frequently block on questions requiring Product Owner input.
• Stakeholders are unable to get decisions or clarity from the Product Owner.
• The Product Backlog items lack sufficient detail or clear acceptance criteria.
• The Scrum Team struggles to define a valuable Product Goal or Sprint Goal.
• There is a perception that the Product Owner is a mere order taker, not a strategic leader.

Initial Conversations and Expectations

Before escalating, start with direct, open conversations. The Scrum Master should facilitate a discussion between the Developers and the Product Owner. The goal is to understand the root cause of the unavailability. Is the Product Owner overloaded? Do they lack understanding of their role's time commitment? Are there external pressures? Clearly articulate the impact of their unavailability on the team's ability to meet Sprint Goals and deliver value. Reiterate the Product Owner's accountability for the Product Backlog, the Product Goal, and maximizing product value.

It is important to set clear expectations based on the Scrum Guide. The Product Owner is an integral part of the Scrum Team. They must be available to answer questions, provide clarity, and make decisions. This is not optional. If the Product Owner cannot meet these expectations, then the organization needs to address the underlying issue, which might include re-evaluating their workload or providing support.

Empowering the Developers (with caution)

While the Product Owner is solely accountable for the Product Backlog, in their absence, the Developers may need to make temporary, well-informed decisions to avoid complete stagnation. This is not ideal, and it should not be a long-term solution. The Scrum Master should coach the Developers on how to make the best possible decisions given the lack of input, always with the understanding that these decisions are provisional and subject to Product Owner review. Document these decisions and their rationale clearly. This transparency will highlight the impact of the Product Owner's absence.

For instance, if a specific detail is missing for a Product Backlog Item, and the Product Owner is unreachable, the Developers might make a reasonable assumption based on past patterns or existing product functionality. They would then proceed, noting the assumption, and plan to validate it with the Product Owner as soon as possible. This minimizes idle time but carries risk. The ultimate accountability for the product remains with the Product Owner.

Involving Management and Organizational Change

If direct conversations and temporary measures do not resolve the issue, the Scrum Master must escalate the problem to management. This is not about blaming the Product Owner, but about highlighting a systemic organizational impediment. The organization must understand that an unavailable Product Owner directly impacts their ability to achieve product goals and realize value. Management may need to reallocate resources, reduce the Product Owner's other responsibilities, or even assign a different Product Owner if the current one cannot fulfill the role effectively.

The Scrum Guide states that the Scrum Master serves the organization in several ways, including helping employees and stakeholders understand and enact an empirical approach for complex work. Addressing an unavailable Product Owner falls squarely into this responsibility. It requires organizational change and support to ensure the Product Owner role is adequately staffed and empowered to succeed.

Start with the Foundations module →

Or take the full Scrum Master track →