The document describes the key roles and responsibilities in Scrum projects. The Product Owner manages the product backlog, prioritizes user stories, and ensures the product meets customer needs. The Scrum Master facilitates the Scrum process and removes impediments for the Delivery Team. The self-organizing Delivery Team develops product increments during each sprint. Area and Epic Owners have broader responsibilities than the Team Product Owner related to finances, customers, and planning at a higher level than individual sprints.

1. SCRUM
Roles and Responsibilities
Maksym Dovgopolyi

2. Product Owner
• The Product Owner manages the Backlog and deciding item priority;
• The Product Owner decides which items from the product backlog are to be
completed first;
• User Stories are usually written by the Product Owner;
• The Product Owner must be familiar with these Stories, and understand the
dependencies between these and User Stories in order to rank (sequence) all Stories
for implementation;
• The Product Owner also sets the schedule for releasing completed work to customers,
and makes the final call as to whether implementations have the features and quality
required for release;
• The Product Owner is Single source of Story truth, Maintaining the Product Backlog,
Interfacing between the Team and the customers and business.
Maksym Dovgopolyi

3. Scrum Master
• The Scrum Master is the person responsible for the Scrum process, making sure it is
used correctly and maximizing its benefits;
• Scrum Master needs to understand Scrum well enough to train and mentor the other
roles, and educate and assist other stakeholders who are involved in the process;
• Scrum Master should maintain a constant awareness of the status of the project (its
progress to date) relative to the expected progress, investigate and facilitate
resolution of any roadblocks that hold back progress, and generally be flexible enough
to identify and deal with any issues that arise, in any way that is required;
• The Scrum Master does not assign tasks to Team members, as task assignment is a
Team responsibility. His general approach towards the Team is to encourage and
facilitate their decision-making and problem-solving capabilities, so that they can
work with increasing efficiency and decreasing need for supervision.
Maksym Dovgopolyi

4. Delivery Team
• The Team is a group of people who do the hands-on work of developing and
testing the product. Since the Team is responsible for producing the product, it
must also have the authority to make decisions about how to perform the work;
• The Team size should be kept in the range from five to nine people, if possible. (A
larger number make communication difficult, while a smaller number leads to
low productivity and fragility);
• Technical Stories are usually written by Team members, and are added to the
Product Backlog;
• Since Scrum is collaborative, team members should be helping each other with
tasks;
• The most effective Scrum teams are self-organized.
Maksym Dovgopolyi

5. Area and Epic owners
• Similar to a program manager, the Area Product Owner is more
concerned with finances and customer relationships rather than day to
day management of tasks (Team Product Owner);
• The Epic owner is similar to a Product owner and owns planning and
decision making responsibilities.
Maksym Dovgopolyi

6. Scrum guys have all the luck!
Maksym Dovgopolyi