Abstract (ROI) · Accepting or rejecting work results ·


Scrum is a
lightweight process framework within which people can address complex problems.
Scrum is subdivision of agile and one of the most favored process frameworks
for implementing agile. Scrum is a highly rigid framework with specific roles
and ceremonies. Scrum methodology follows iterative software development model
used to manage complex software and product development. Fixed-length
iterations, called sprints, lasting one to two weeks, allows the team to ship software
on a regular basis. At the end of each sprint, stakeholders and team members
meet to plan the next steps. The article described about the roles and
responsibilities followed in the Scrum practices.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!

order now


picture depicts the Scrum framework



Major points made
by Author

The article was
presented to describe about the size of the project team, structure of project
team and project participants roles & responsibilities in Scrum
methodology. Usually Scrum team consists of 3 to 9 professionals, and it works
efficiently when there is proper coordination and collaboration among the team
members. Scrum of Scrum (SOS) is multiple scrum teams coordinating and working
on the same product or towards the same objective,

There are three
specific roles in scrum:

Product owner:
The scrum product owner has the vision of what shall be prioritized to build and
conveys that vision to the team. The roles of the product owner are:

Defining and
prioritizing the features of the product backlog

Deciding on the
release date and content

Responsibility for the
profitability of the product (ROI)

Accepting or rejecting
work results

Adopting changes in
features and priorities at every iteration

Removing obstacles and
shielding the team from interference

Responsibility for
improving performance of the team, ensuring the team is fully functional and

Attending daily
stand-up meeting, iteration reviews, and planning meetings

Scrum master:
The scrum master is the one who helps the team to do their best possible work. The
major responsibilities of this role are:

Organizing meetings
(stand-up meetings)

Making sure that the
team follows scrum processes

Dealing with
roadblocks and challenges

Working with the
product owner to ensure that the product backlog is ready for the next sprint

Having responsibility
and authority over the process but not over the team

Scrum team:
The scrum team owns the plan for each sprint and they anticipate how much work
they can complete in each sprint. They are:

(including testing)

Assists product owners
in planning the acceptance tests and performing the test run.

Generate testing plan
and also quality metrics

self-organizing/managing group of individuals with autonomy regarding how to
achieve commitments

Independent within
project guidelines to do everything to reach the iteration goal

Meetings in
scrum:  Following are the different type of meetings

Product backlog:
Every scrum project is driven by a product and the vision of the product owner.
The product owner and scrum team meet to prioritize the items on the product
backlog (the work on the product backlog comes from user stories and
requirements). The product owner projects the objectives in a product backlog,
and then creates a priority list of what is required based on the value it
creates for a customer or a business. The highest value item is at the top of
the list.

A product
backlog helps the product owner keep track of all the features that
stakeholders would like to include in the product. In other words, the product
backlog is kind of like a wish list of all possible features in the final product.
The product backlog evolves over the lifetime of the project and items are
reprioritized (they can be removed as well). Anyone can add features to the
product backlog, with the product owner prioritizing each one:

Unlike a sprint
backlog, the product backlog is always changing and improving

Anyone can put
anything on the backlog, but the product owner has the final authority

Most scrum teams use
user stories as product backlog items

planning: Before each sprint, the product owner presents the top items on the
backlog to the team in a sprint planning meeting. In the sprint planning:

The product owner
presents a backlog to the scrum master and team

A spring backlog is

The meeting is
attended by the product owner, scrum master, and the entire scrum

Outside stakeholders
may attend by invitation of the team (but this is rare in most companies)

Depending on the
sprint length, the sprint planning meeting could be different

scrum/stand-up: The daily scrum is a 15-minute stand-up meeting where team
members talk about their goals and any issues that have come up:

It is typically held
in the same location and at the same time each day

The team
self-organizes to improve performance

New daily plans for
implementation and impediment removal are deliverable

It is also known as a
daily huddle or morning roll-call

They stand up to keep
the meeting short

Sprint review:
At the end of each sprint the:

Team presents a
backlog that is DONE to the product owner and stakeholders.

Velocity are
deliverable (what the product owner confirms is DONE),

as well as feedback
(used to update the product backlog) and potentially shippable product

For each week of the
sprint duration, apply one hour of meeting time for customer reviews.

Why is the
article important?

The article clearly points out the responsibilities of Scrum roles and recommended
the procedures to be followed while distributing the work among the Scrum teams.
Understanding defined roles and responsibilities in a Scrum project is very
important for ensuring the successful implementation of Scrum. Scrum fundamentals
can be applied to any type of project in any organization and must be adhered
to in order to ensure effective implementation of the Scrum framework. Agile
methodologies suggest that team members be largely responsible for managing
their own processes, making decisions about how project objectives will be
attained, and transferring task responsibility to various team members. When an
organization decides to adopt Scrum, the main important things to understand is
how Scrum roles differ from traditional project execution roles.

How Does the
Article Relate to the Class?

The roles defined in the textbook were very brief and the article helps
in understanding the scrum team structure and very well-defined Scrum roles &
responsibilities. This also helps defining the responsibilities of scrum roles
during scrum project implementation.

Conclusions and

Implementation of agile PM methodologies is related to improvement of
development process: less bugs, faster delivery, more and effective
communication, better quality, better risk analysis, less over costs etc. But
analyzing results of existing researches have been concluded that there are lot
of problems in the project team that may affect application of the agile PM
methodology and successful implementation of the project. First of all,
preparation of team is needed before implementation of the new agile PM
methodology. With the proposed method is possible to analyze the team structure
and motivation and adapt agile roles, artefacts, processes and practices that
are more suitable for the project team with target to improve team
self-organization, motivation and effectives.