It has been proved by surveys that additional certifications
such as ITIL, PRINCE2, PMP and Scrum can not only help a professional (IT or
non-IT) gain more knowledge regarding success in their projects, but also help
an organization in which he/she works in the long run. One of the most similar
facts that can be seen from these certifications is that they all emphasize the
importance of roles and non-roles in their projects. In this article, the
emphasis is placed on roles and non-roles of an organization. In Scrum training
or Scrum certification, a lot of time is dedicated to defining and
understanding roles and responsibilities for the success of every project.
The roles of Scrum fall into two categories, i.e., core and
non-core roes. In Scrum, core roles are defined as the roles that are
mandatorily considered necessary for production of the project, they are and
should be committed to the specific project and also responsible for success in
every Sprint of the project and for the entire project. Non-core roles are
those roles which are not mandatory in a Scrum project. The roles may consist
of members interested in the project though they might not have any formal role
in the team. But they are given permission to interact with the members of
team. They may or may not be responsible for the outcome of the project. But in
Scrum, it has been clearly specified that these roles should also be
considered.
Core Roles are further divided into three and they are held
responsible for meeting the objectives of the project. Commonly referred to as
the SCRUM core team, they are known by the names: Product Owner, Scrum Master
and Scrum team. But the important fact to be taken into account is that these
roles have or given no authority over other roles. Let us first consider the
role of Product Owner. The responsibility of maximization of business value in
a project is assigned to this role. It includes articulating requirements of
the customer and maintenance of justification of business about the project. In
short, Product Owner can be defined best as the Voice of the Customer.
Next is the Scrum Master role. Scrum Master can be best
described as the person who ensures that the environment in which the team
works is as per the guidelines that are required to develop the product or
service successfully. Finally, the Scrum Team is a group of members responsible
for understanding the requirements of the business as specified by the Product
Owner, who estimates User Stories and creating the project Deliverables.
No comments:
Post a Comment