Scrum defines three roles: Scrum Master, Product Owner, and Development Team. Together all three roles make up a Scrum Team.
The Product Owner defines the what--as in what the product will look like and what features it should contain. The Product Owner is expected to incorporate stakeholder feedback to create the highest value product increments each and every sprint. Product Owners maintain the product backlog and ensures that everyone knows the priorities.
Like Scrum Masters, product owners vary in their specific mix of skills and qualifications, but most product owners work toward developing:
The Development Team decides how to accomplish the work set forth by the Product Owner. Development Teams are structured and empowered to organize and manage their own work. The resulting synergy optimizes overall efficiency and effectiveness.
According to the Scrum Guide, development teams have the following characteristics:
The ideal size for a development is between 3 and 9 people, not including the Scrum Master and product owner. Any smaller and the team couldn’t accomplish enough each sprint. Any larger and communication becomes complex and cumbersome.
The Scrum Master helps the Scrum Team perform at their highest level. They also protect the team from both internal and external distractions. Scrum Masters hold the Scrum Team accountable to their working agreements, Scrum values, and to the Scrum framework itself.
Entire books have been written on what makes a great Scrum Master, but most experts generally agree on the following:
According to the Scrum Guide, the Scrum Master serves the Product Owner by:
According to the Scrum Guide, the Scrum Master serves the Development Team in several ways, including:
The Scrum Guide describes the Scrum Master as serving the organization by: