Collaborating with the Product Owner: How to foster strong synergy?

A well-functioning Scrum team's success hinges on the collaboration between the Product Owner and the rest of the team. However, this collaboration isn't always smooth sailing. Where does the Product Owner's role end and the Scrum Master's or Development Team's begin? How do you prevent the Product Owner from becoming a 'client' rather than a team player?

The key lies in open communication, clear responsibilities, and a shared focus on delivering value. In this article, we explore how to collaborate optimally with the Product Owner to elevate the team and the product.

‍

What is the Product Owner's role in the team?

The Product Owner (PO) is responsible for the 'what' and the 'why' of the product. They determine:

• What needs to be built (and what doesn't).
• Which priorities are key to deliver the most value.
• What the product's vision and goals are so that everyone works in the same direction.

But the PO doesn't do this alone. Collaboration with the Development Team and the Scrum Master is essential to ensure that the team is both effective and efficient can work.

‍

How to ensure strong collaboration?

1. Work as one team, not as 'client and supplier'

Sometimes teams see the Product Owner as someone who assigns tasks and then waits for the work to be done. This is counterproductive. Strong collaboration means that the PO and the team share responsibility for the product.

What helps?

• Actively involve the PO in Sprint Planning and refinements, so that the team understands why certain choices are made.
• Encourage two-way communication: the PO prioritizes work, but the team can also make suggestions.
• Ensure direct communication. A PO who only shows up at the Sprint Review misses crucial interactions.

‍

2. Make backlog management a shared responsibility

The Product Backlog formally belongs to the Product Owner, but a well-maintained backlog is a joint effort.

How to approach this practically:

• Hold regular Backlog Refinement sessions where the team and the PO work together on the backlog.
• Ensure the backlog doesn't just contain features, but also technical improvements. A good product doesn't just consist of new functionalities, but also robust architecture.
• Keep the backlog organized and avoid endless lists of tasks that are never picked up.

‍

3. Speak the same language: focus on value

A common pitfall is that the PO speaks in terms of business value, while the team thinks in terms of technical solutions. This can lead to miscommunication and frustration.

What works well?

• Use user stories and acceptance criteria that are understandable to everyone.
• Define 'value' together. This can be user impact, but also technical improvements that support the long term.
• Regularly ask the question: "Why are we doing this?" A team that understands the true value makes better decisions.

‍

4. Foster open and continuous communication

Collaboration with the PO should not be limited to a few fixed meetings per Sprint.

Tips for better communication:

• Use short check-ins outside of standard Scrum events to quickly discuss questions or ambiguities.
• Keep the feedback loop short. Show work to the PO early to prevent surprises.
• Encourage constructive discussions. The PO should be open to input from the team and vice versa.

‍

5. The role of the Scrum Master in this collaboration

The Scrum Master plays a crucial role in strengthening the collaboration between the Product Owner and the team.

What can the Scrum Master do?

• Help the PO with backlog management and prioritization if this proves difficult.
• Support the team and the PO in effective communication and collaboration.
• Ensure that the PO is not overloaded with operational tasks that the Development Team can handle.

A strong Scrum Master coaches the Product Owner on how they can collaborate optimally with the team, without becoming a 'middleman'.

‍

Common mistakes in collaborating with the Product Owner

1. The Product Owner is not involved in daily interactions.
   → Ensure the PO is not an outsider, but an integral part of the team.
2. The backlog is a mess.
   → Keep the backlog clear, structured, and value-driven.
3. The team only receives ready-made tasks without context.
   → Collaborate on stories, so everyone understands why something is important.
4. There is too little room for technical improvements.
   → The PO must prioritize between features and technical maintenance tasks together with the team.
5. Communication only happens at the end of the Sprint.
   → Regular alignment prevents surprises and inefficiency.