Scrum Non-core Roles – An Insight

May 5, 2020
By

In Scrum the non-core roles are those roles which are not mandatorily required for the Scrum project. They may not be continuously or directly involved in the Scrum process. They are not accountable for the success of the Scrum Project. However, knowing non-core roles is important as they could play a significant part in the projects.

 

Non-core roles can include the following:

  1. Stakeholder(s)

Stakeholder(s) is a collective term that include customers, users, and sponsors, who frequently interface with the Product Owner, Scrum Master and Scrum Team to provide them with inputs and facilitate creation of the project’s product, service, or other result. Stakeholder(s) influence the project throughout the project’s development. Stakeholders may also have a role to play during some of the important processes in Scrum.

Customer – The customer is the individual or the organization that acquires the project’s product, service, or other result. For any organization, depending on the project, there can be both internal customers (i.e., within the same organization) or external customers (i.e., outside of the organization).

Users – Users are the individual or the organization that directly uses the project’s product, service, or other result. Like customers, for any organization, there can be both internal and external users. Also, in some industries customers and users may be the same.

Sponsor – The sponsor is the individual or the organization that provides resources and support for the project. The sponsor is also the stakeholder to whom everyone is accountable in the end.

At times, the same person or organization can play multiple stakeholder roles; for example, the sponsor and the customer may be the same.

  1. Vendors

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

  1. Scrum Guidance Body

 The Scrum Guidance Body (SGB) is an optional role but highly recommended to formalize organizational practices related to Scrum. It generally consists of a group 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 Scrum Guidance Body also helps capture the best practices that should be used across all Scrum projects in the organization.

 

For more articles, please visit: www.scrumstudy.com/freeresources/free-blogs-and-articles

Share

Leave a Reply

Your email address will not be published. Required fields are marked *

Subscribe

Follow Us On