Can Scrum Master and Product Owner be the Same Person?

In the agile world, the Scrum framework stands out for its emphasis on having clear roles and accountabilities, so that everyone in the Scrum Team can collaborate effectively. More specifically, the Scrum Guide clearly mentions that for a Scrum Team to perform, it needs a Scrum Master and a Product Owner.

In real Scrum practice however, you’ll be faced with many situations that are going to be different to what the Scrum Guide prescribes, such as not having a complete Scrum Team. Many Scrum Teams, especially in smaller companies or ones that are just starting out, find themselves facing a common issue: the absence of a dedicated Scrum Master or Product Owner.

This situation is usually caused by limited team sizes, where there are not enough people within the team to serve as a dedicated Scrum Master or Product Owner. As a result, these teams find themselves having to look for alternative solutions, such as having one person in the team to serve as both the Scrum Master and Product Owner.

What to Consider in This Situation

While it's not an ideal arrangement, having one person double up as both Scrum Master and Product Owner is preferable to having either role missing. Understandably, this may not feel like a perfect solution. However, in practical Scrum scenarios, you need to be resourceful in enabling your team so they can continue to deliver valuable work, even in less-than-ideal conditions.

If you do find yourself in this situation, it’s important to make sure that all core accountabilities of both roles are adequately covered, allowing the team to effectively build and deliver their work. Also remember to keep an eye on how the team is working together, and make regular, small improvements as you learn something new.

However, you should also consider the potential issues that may arise when you consolidate the Scrum Master and Product Owner role. The most apparent is the risk of high workload as one person juggles the responsibilities of two distinct roles. Additionally, the roles of Scrum Master and Product Owner require a degree of objectivity, which is challenging to maintain when both roles are merged.

What to Do Next

Considering the potential issues, it's important to view this as a temporary solution and proactively seek to improve the conditions around your team’s completeness.

You can do this by acknowledging the issue openly, and discuss it with your team and leaders. Highlight how this arrangement impacts your team’s performance and productivity. Investigate the underlying reasons for not having separate individuals in these roles and engage with key leaders or decision-makers in your company to move towards having a dedicated person for both the Scrum Master and Product Owner roles.

As with any activities that involve making organisational changes, this will take some time. What matters is that you consistently take necessary actions to create better conditions.

Conclusion

If your situation calls for it, having one person double up as both Scrum Master and Product Owner is preferable to having either role missing. However, you should see this as a temporary solution and consistently take the necessary actions to separate the two role. This approach will significantly enhance your team's long-term performance.

These types of situations show how flexibility and adaptability play a big part in navigating the real-world challenges of Scrum. Since you cannot instantly shape everyone and everything around you to align perfectly with the Scrum Guide, what you can do is maximise what’s possible with what you have, and slowly influence the conditions around you to improve.

This ability to adapt and influence is what separates the successful and not so successful Scrum teams in the industry.

———

Want to learn Scrum at your own pace?

Sign up to our top-rated Scrum course that has helped thousands of students become expert Scrum practitioners.

Or talk to us today to improve your team’s performance using the Scrum framework.