Product ownership: what to do when the product owner is absent - professional agile coach

The role of the Product Owner (PO) is fundamental in the Scrum methodology. They are responsible for maximizing the value of the product resulting from the development team's work. But what happens when the PO is absent? This situation, although unexpected, can create uncertainty and delays if not handled properly. In this article, we will explore strategies and solutions to maintain product ownership and ensure project continuity during the Product Owner's absence.

Why is Product Ownership Crucial?

Product ownership, in essence, refers to the responsibility and authority to make decisions about the direction and development of a product. The Product Owner is the main guardian of this ownership. Their knowledge of the market, of the users and of the product vision is essential to guide the team. Maintaining product ownership, even in the PO's absence, ensures that:

• Decisions are made aligned with the product strategy.
• The development team has a clear direction and avoids confusion.
• The product's value for users and the business is maximized.
• The risks of deviations and rework are minimized.

Common Causes of Product Owner Absence

Product Owner absences can be unplanned or scheduled. Some of the most common causes include:

• Vacations or Leave: The PO, like any other team member, has the right to take a break.
• Illness: Sudden illnesses may force the PO to be absent from work.
• Role Change: In some cases, the PO may be reassigned to another project or leave the company.
• Participation in Events or Training: The PO may need to attend conferences, workshops, or training courses to improve their skills and knowledge.
• Work Overload: In high-demand situations, the PO may be overloaded and need to delegate responsibilities.

Strategies to Maintain Product Ownership During the PO's Absence

The key to managing the Product Owner's absence lies in planning and preparation. Here we present some effective strategies:

1. Appoint a Backup Product Owner

Best practice is to designate a team member who can act as a backup Product Owner in case of absence. This backup should:

• Have a deep knowledge of the product and its vision.
• Understand the needs of users and the business.
• Be familiar with the product backlog and priorities.
• Have the authority to make decisions on behalf of the PO.

Ideally, the backup should be someone from the development team who has worked closely with the PO and who understands the product's priorities and strategy. This person should be prepared and trained to assume the PO's responsibilities temporarily.

2. Comprehensive Documentation of the Product Backlog

A well-documented product backlog is essential to ensure project continuity. The backlog should include:

• Clear and concise user stories.
• Defined acceptance criteria.
• Clear prioritization of user stories.
• Relevant notes and comments.

The more detailed and up-to-date the backlog is, the easier it will be for the development team to understand the product's needs and objectives, even in the PO's absence.

3. Clear and Transparent Communication

Communication is essential to keep everyone informed and aligned. Before the PO's absence, it is important to clearly communicate:

• The expected duration of the absence.
• Who will act as the backup Product Owner.
• The responsibilities of the backup.
• How decisions will be made during the absence.

During the absence, the team should maintain regular communication with the backup and with the PO, if possible. This will help resolve any questions or issues that arise.

4. Backlog Refinement Meetings

Backlog refinement meetings are an excellent opportunity to clarify doubts and ensure that all team members understand the user stories. During the PO's absence, these meetings are even more important.

The backup Product Owner should lead these meetings and ensure that all user stories are well defined and prioritized.

5. Empower the Development Team

In the absence of the Product Owner, it is important to empower the development team to make decisions. This means:

• Trusting the team's judgment.
• Delegating responsibilities.
• Encouraging collaboration and communication.

An empowered development team is more proactive and capable of solving problems independently.

Key Roles to Maintain Continuity

In addition to the backup Product Owner, other key roles can help maintain continuity during the PO's absence:

• Scrum Master: The Scrum Master can facilitate communication, resolve conflicts and ensure that the team follows Scrum principles.
• Technical Lead: The technical lead can provide technical guidance and help the team make implementation decisions.
• Business Analyst: If the project has a business analyst, they can provide insight into the business's and the users' needs.