Overview
Recently, I attended a Certified Scrum Master training, and I felt the need to organize my thoughts on the differences between a Scrum Master and a Product Owner, so I decided to write this article.
cf. Became a Certified Scrum Master (LSM)
What is a Scrum Master?
Responsibilities
- Responsible for establishing and ensuring the effectiveness of Scrum
- Ensures that Scrum is practiced correctly by helping the Scrum team understand Scrum theory and processes
- Enables the Scrum team to improve processes based on the Scrum framework
Roles
- Improve team performance
- Improve processes
- Remove impediments (interruptions)
- Facilitate Scrum events
- Visualize work
- Achieve goals
- Not a manager or administrator
What is a Product Owner?
Responsibilities
- Responsible for maximizing the value of the product
- Responsible for managing the product backlog
Roles
- Clarify the product vision
- Set product goals
- Define release plans
- Manage budget
- Create the product backlog
- Have authority over the priority of product backlog items
- Ensure the product backlog is complete
- Collaborate with stakeholders
Differences Between Scrum Master and Product Owner
The Scrum Master is concerned with the process (≒How), while the Product Owner is concerned with the product's value and vision (What and Why).
In practicing Scrum, the Scrum Master is responsible for understanding Scrum, evangelizing it to the team, and improving processes, while the Product Owner makes decisions to maximize the product's value.
Personal Thoughts
From a personal perspective, it is not recommended to hold both the Scrum Master and Product Owner roles simultaneously, but there seems to be an atmosphere where holding both the Scrum Master and developer roles is acceptable. However, whether one can fully fulfill the responsibilities of each position is questionable. In situations where there aren't enough resources to have a dedicated Scrum Master, how about a setup with a dedicated Scrum Master (responsible for Scrum Master duties, possibly serving multiple teams) and a developer who also acts as a Scrum Master (in a supportive, leadership role)? This is somewhat similar to the environment I have experienced.
