Scrum Roles

This lesson is part of the course The Scrum Crash Course . Use navigation on the left.

In contrast to the traditional project management methods, Scrum doesn’t have or need a project manager, task manager, or team lead. The Scrum team includes the Product Owner, Scrum Master, and the Scrum Delivery Team. The scrum delivery team is made up of technical team members only.

scrum roles

Product Owner

Product owner is responsible for the product’s success. While the delivery scrum team is responsible for delivering a quality solution, the product owner is responsible for knowing the market for the product. The product owner should understand the user’s needs well enough, to guide the team toward a marketable release sprint after sprint.

There are different types of product owners in different types of projects, but regardless of the technical situation or the desired outcome, there should be one (and only one) product owner who makes final decisions about the direction of the product and the order in which features should be developed.

The product backlog, or list of items to be completed by the Scrum team, is prioritized by the product owner so as to reflect his most valuable requests or changes for the product in development. The product owner, since he is representing the “what” and “why” of the system, should be available to the team to have regular dialogs about the requirements in the product backlog.

The product owner must make the product vision clear to everyone on the team and regularly maintain the product backlog in keeping with the product vision. The product owner always keeps the next set of product backlog items in a ready state so that the team always has work in the queue for the next sprint.

Scrum Master

Scrum Master is responsible to ensure product development flows as smoothly as possible.  Scrum Master, also called “The Servant Leader”, protects team members from interruptions and keeps them focused on their sprint commitments. Scrum Master also helps the product owner to get the product backlog in order.  

Scrum Masters facilitate all Scrum meetings, ensure that everyone on the team understands the goals, and share a commitment together as a true team and not just as a collection of individuals. 

The Scrum Delivery Team

The Scrum team huddles around a problem (traditionally speaking, a requirement) from an ordered list known as the Product Backlog and delivers solutions. Scrum teams should be five to nine team members, dedicated to the life of the project (and perhaps beyond). They should be cross-functional, empowered, and self-organizing. Scrum teams plan, estimate, and commit to their work, rather than a manager performing these functions for them.

The goal of the team is to deliver a shippable product increment that meets an agreed-upon Definition of Done by the end of each and every Sprint.

You might be interested in the following courses:

Course Category: Development Methodologies

  • The Scrum Crash Course

    by Ajay Kumar Konda

    Scrum is simple; it consists of six time boxes (one of which is optional), three roles, and three ‘official’ artifacts. A sprint, the first of the six time boxes, is an iteration defined by a fixed start and end date; it is kicked off by sprint planning and concluded by the sprint review and retrospective. The […]

  • The Scrum Master's Responsibilities

    by Ajay Kumar Konda

    A ScrumMaster must have a deep understanding of the Scrum framework. The job of a scrum master is to help the customer and the team to work very closely ensure expected deliveries. Scrum Master facilitates the team members to reflect upon ways that they can improve their day-to-day communication and processes. It is the responsibility […]

  • Understanding The Agile Methodology

    by Ajay Kumar Konda

    Agile Methodology refers to the software development methodology that is centered around the idea of iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.  The various Agile Methodologies share much of the same philosophy, many of the same characteristics and practices. But from an implementation standpoint, each of these methodologies has […]

Back to: The Scrum Crash Course > A Quick Guide