Similar to the
importance given
to roles in Scrum training or Scrum certification,
much emphasis has also be given to Non-roles in a project. They are best
defined as the roles that are not necessarily needed for the Scrum project
as well as can be or not be directly affiliated or involved in any part of
the scrum process. But it is mandatory that non-roles are
also taken into consideration since they can play a significant role in some of
the projects. The non-core roles are discussed below:
Stakeholder:
Usually described as a
term to include not only customers, but also the users, sponsors who generally
take interest in the product or service to have interaction with the Product
Owner, Scrum Master and Scrum team to not only provide
inputs but also help in creation of the service, project’s product or other
duties. Their inputs are needed during the Create Prioritized Product Backlog,
Conduct Release Planning, and Retrospect Sprint in addition to other processes
in Scrum.
Customer:
In Scrum training,
the customer can be defined as the individual or organization that can acquire
the project’s product/service/other result. In every organization, as per the
project, they can be divided into internal customers (within the same
organization) or external customers (outside the organization).
Users
An individual or an
organization that uses the product or service of the project or any other
liability can be defined as a user. Similar to customers, in every organization
there can be internal/external users. In some circumstances, customers and
users may be classified as one and the same.
Sponsor
An individual/group of
individuals or an organization that provides resources and support for the
implementation and journey of the project. The sponsor can be defined as the
key stakeholder whom everyone should be accountable at the end.
There can be instances
in which a person/individual or organization can play
multiple roles (such as sponsor/customer might play the same role).
Vendors
External (Individuals
or organizations) which provide products/services that do not come under the
jurisdiction of the core competencies of the project organization.
One of the important
optional roles that are followed in Scrum training is
that of the Scrum Guidance Body (SGB). This body usually consists of
a group of documents and/or group of experienced professionals involved in
defining objectives with regards to government regulations, security, quality
and other essential parameters. The guidelines imposed by this body is given
due importance by Product Owner, Scrum Master and
the Scrum team.