Ever wondered how a Scrum Master differs from a Product Owner in a Scrum environment? John McFadyen walks us through his interpretation of how they differ.  

A scrum master and a product owner are completely different sides of a scrum team and perform very different functions within the environment.  

A product owner acts as the CEO of the product.  

They determine the vision for the product and articulate that vision to the scrum team to help inspire creative solutions to solving problems or creating products that delight customers.  

The product owner is also responsible for creating a backlog of items, in order of priority, to help the development team understand what needs doing and why it needs doing.  

A product owner will also be responsible for writing epics and user stories that aim to provide context to the development team, helping them to understand what the specific feature or item aims to do for the user and why it is important to the user that the new feature or item exists.

A product owner also works closely with product stakeholders within the organisation as well as outside the organisation to ensure that the most valuable products are being built. They also work closely with customers to understand their challenges and ensure that the products and features being built will truly delight those customers.  

A scrum master works with the product owner to achieve their vision and ensure that great products, services and features are being built.  

A scrum master will work with the development team to help them excel in the environment and ensure that there are no impediments to the team's progress.  

Sometimes, that involves working with people outside of the scrum team to remove impediments or secure resources that will help the scrum team to thrive.  

A scrum master also acts as a coach to the development team, helping them to identify the most effective ways to solve complex problems or create valuable products.  

A scrum master does not carry the same authority as a project manager nor do they involve themselves in the tiny details in the same way that a project manager would.  Instead, they focus on coaching others or facilitating events such as retrospectives to help the team gain the most valuable insights and learning from each sprint and product increment.  

A scrum master works with influence rather than authority and as such they are trusted figures within the scrum team.

They are great at coaching and facilitation rather than issuing directives and as such they can be very effective at helping scrum teams tap into their highest potential.  

A scrum master understands that members of the development team are the experts when it comes to solving problems or creating products, and as such, doesn't interfere in the minor details of their work. Instead, they work with the development team to identify ways to improve in each cycle and how to integrate what has been learned in each iteration into the scrum team repository.  

If you would like to become a scrum master, visit our Certified Scrum Master course page on https://www.agilecentre.com/courses/scrum-master/certified-scrummaster/

If you would like to become a product owner, visit our Certified Scrum Product Owner course page on https://www.agilecentre.com/courses/product-owner/certified-scrum-product-owner/ 

If you like the idea of mentored and coach-driven skills development, visit our Agile Coach Academy on https://www.agilecentre.com/courses/agile-coach/agile-coach-academy/ 

If you would like to understand how coaching integrates into the scrum master role and begin your journey there, visit our on-demand Introduction to Coaching course on https://agile-centre.thinkific.com/courses/introduction-to-coaching