Imagine a duet between a pianist and a violinist. Separately, they can produce beautiful solo music, but together they can create a symphony. The same goes for the Product Owner (PO) and the Scrum Master. The PO and the Scrum Master are two crucial roles within Scrum. Although they have different responsibilities, they must work closely together to ensure a successful product. In this article, I will discuss the collaboration between the two roles. I will give you an insight into the benefits of strong collaboration, for the team, the customer, and the organization. But I will also show you what the signals are and what goes wrong when they do not work well together. To introduce both situations, I will start with a short story of two scrum teams; the Agile Avengers and the Chaos Crew. Then I will tell you a bit more about the individual roles and how they complement each other. I will conclude with some tips on how to improve collaboration.
“Talent wins games, but teamwork and intelligence win championships“
– Michael Jordan
The effect of bad and good cooperation
Not so long ago, in a software land not far from here, there was a Scrum team called Chaos Crew. In this team, the PO and Scrum Master were in constant conflict. The PO was laid-back and flexible, while the Scrum Master was strict, pushy and rule-bound. Their meetings were battlefields, their communication resulted in endless discussions and they were unable to work together effectively. The impact on the team was clear: development fell behind schedule, team members became frustrated and the Product Backlog became an unmanageable mess.
On the other hand, there was another Scrum team called Agile Avengers. In this team, the PO and Scrum Master worked side by side. The PO was visionary and results-driven, while the Scrum Master was disciplined, committed, and process-oriented. Together, they formed a dynamic duo, and their collaboration was cutting edge. They complemented each other, overcame obstacles, and led their team to unprecedented heights of success; the team became high-performing. Their communication was seamless, they had respect for each other, and their ability to work as a unit was impressive.
The above two scenarios illustrate the importance of a healthy collaboration between the PO and the Scrum Master. If the PO and Scrum Master work well together, this results in success for themselves, but especially for the developers, the customer and the organization. I will explain this later, after I tell you a bit more about the differences in the roles, but also where the roles overlap.
Two different roles, with one thing in common
To understand how the PO and Scrum Master work together, we first need to understand their individual roles. The PO is not just someone who decides what to build. The PO represents the interests of the customer, stakeholders, and the business. To do this, the PO must understand and balance both the market needs and the team’s capabilities. This also means that the PO must make tough decisions about priorities and scope. The Scrum Master is the guardian of the process and ensures that the team is not distracted or overloaded. Furthermore, the Scrum Master facilitates the Scrum rituals (Sprint, Sprint planning, Daily Stand-up, Retrospective, and Sprint Review) and ensures that the team functions like a well-oiled machine.
Both are committed to maximizing the team's potential and realizing value. They are in a leadership role, but their perspectives are different.
The PO is focused on the product vision, while the Scrum Master is focused on the process. They complement each other like a pianist and a violinist in a duet: the PO sets the tone with a clear vision and priorities, and the Scrum Master ensures the rhythm and harmony in the team.
A classic pitfall is that the PO and Scrum Master see each other as opponents, with conflicting goals. They can get caught in power games or miscommunication. Open communication and mutual respect are essential to avoid such a situation. By working together, they can identify and solve problems faster.
The result of good cooperation
For the developers First of all, this means clarity. Seamless communication between the Scrum Master and Product Owner ensures that requirements, expectations, and priorities are clear, which drastically reduces the chance of confusion and misunderstandings. Furthermore, with less friction and potential conflict, developers can focus on what they do best: building great products. Furthermore, when working well together, they receive the necessary support and visionary direction from the PO and Scrum Master that helps them excel in their work.
For the customer This harmonious collaboration translates into a higher quality product that more closely matches their needs and expectations. Furthermore, with more efficient sprints and faster deliveries, customers see the fruits of their investment sooner. When they see that the PO and Scrum Master are on the same page, they have more confidence in the product and process; customers can count on promises being kept and their feedback being taken seriously.
As for the organization, it benefits from greater efficiency. Well-aligned teams waste less time on miscommunication. This positive outcome also has an impact on the market: successful projects and satisfied customers strengthen the reputation of the organization. And ultimately, from a business perspective, good collaboration between the PO and Scrum Master leads to a better product in less time, resulting in a better return on investment (ROI) for the organization.
As you can read, there is much to gain when the PO and Scrum Master work well together. And now? How do you tackle this? Here are some recommendations.
What steps can you take NOW to improve collaboration?
As a PO and Scrum Master, you can do a lot to improve collaboration. A PO can (continue to) share a vision and provide clear and detailed requirements, so that the Scrum Master and the team know exactly what is expected. Providing timely feedback and protecting the team from changing priorities is also essential.
On the other hand, the Scrum Master can help the PO with a smooth process to focus on the content side. In concrete terms, this can mean: simplifying stakeholder management, helping to clarify requirements or facilitating sessions to refine the backlog.
In addition, there are a few things you can both do to increase trust and thereby improve cooperation:
- Plan joint sessions (e.g. weekly or every sprint) to align expectations. You can also have coffee together every morning to review the day, so you are always aware of each other's challenges and can quickly adjust where necessary, without being in a super formal setting.
- Get to know each other's work better. Perhaps the Scrum Master can shadow the PO for a day and vice versa. This will give you a better idea of what the other person does, what challenges there are and where you can support each other.
- Make time for regular (weekly or bi-weekly) feedback moments.
- Invest in team building activities to strengthen mutual respect and trust.
Summary:
The collaboration between a Scrum Master and Product Owner is crucial to the success of any Scrum team. As the story of the Agile Avengers and Chaos Crew shows, good collaboration can lead to a high-performing team, while poor collaboration can lead to frustration and failure. Building a strong collaboration between the Scrum Master and Product Owner requires a commitment to each other; open communication, mutual respect, and continuous improvement are key to this. By working together as a unit, they can lead their team to success and deliver value to both the customers and the organization.
Do you have an anecdote about a hilarious or dramatic collaboration between a PO and a Scrum Master? Share your story in the comments, so we can learn together through laughter (or tears)!
