Articles

When implementing Scrum, sooner or later steam members ask, “So, what am I supposed to do?” Understanding defined roles and responsibilities in a Scrum project is extremely important for helping the team implement the framework successfully.

Scrum roles fall into two broad categories, core and non-core:

Core Roles—Core roles are those roles which are mandatorily required for producing the project’s product or service. Individuals who are assigned core roles are fully committed to the project and are ultimately responsible for the success of each sprint and that of the project as a whole. Those filling these roles are often referred to as the Scrum Core Team.

These roles include:

The Product Owner is the person responsible for achieving maximum business value for the project. He or she is also responsible for articulating customer requirements and maintaining business justification for the project. The Product Owner represents the Voice of the Customer.

The Scrum Master is a facilitator who ensures that the Scrum Team is provided with an environment conducive to completing the project successfully. The Scrum Master guides, facilitates, and teaches Scrum practices to everyone involved in the project; clears impediments for the team; and ensures that Scrum processes are being followed.

The Scrum Team is the group or team of people who are responsible for understanding the requirements specified by the Product Owner and creating the deliverables of the project.

Non-core Roles—Non-core roles are those roles that are not mandatorily required for the Scrum project. They may include team members who are interested in the project but have no formal role in the project team. These individuals may interface with the team but may not be responsible for the success of the project. The non-core roles should be taken into account in any Scrum project.

Non-core roles include the following:

Business Stakeholder(s), which is a collective term that includes customers, users, and sponsors who frequently interface with the Scrum Core Team and also influence the project throughout the project’s development. Most importantly, it is for the business stakeholders that the project produces the collaborative benefits.

Vendors, include external individuals or organizations that provide products and/or services that are not within the core competencies of the project organization.

Scrum Guidance Body (SGB) is an optional role, which generally consists of a set of documents and/or a group of experts who are typically involved with defining objectives related to quality, government regulations, security, and other key organizational parameters. The SGB guides the work carried out by the Product Owner, Scrum Master, and Scrum Team.

This figure illustrates a typical interaction between the Scrum Core Team members, one type of Business Stakeholder, and the customer.

The Scrum Core Team roles are essential for all Scrum projects, while the non-core roles will vary according the individuality of each company, project and group of business stakeholders.