The document outlines the roles and responsibilities of the Product Owner, Scrum Master, and Team Member in a Scrum process. It describes that the Product Owner is responsible for maintaining the product backlog, release planning, prioritizing features, and accepting completed work. The Scrum Master facilitates meetings, removes impediments, and protects the team. Team Members work on tasks, update status, and share ideas to improve.

1. • I keep Product Backlog up • I prepare release & sprints • I am chicken and silent
to date plan Ask me questions and I will
answer.
• I manage features and • I support team during
• I prioritize new tasks and decide
stories sprint planning when they should be
• I add details and • I estimate business value, implemented
acceptance criteria • I do not estimate • I change sprint backlog if it is
• I manage priorities complexity (size) really necessary
Backlog Planning Daily scrum
• Only I will accept or not • If I attend, I am chicken
implementation team has
done
during the meeting
• I ask what was not completed • If I have some ideas, I
• I decide what to do with will add them
incomplete work (move to
backlog, to next sprint,
forget)
Review (Demo) Retrospective
Scrum Cookbook, by Dusan Kocurek, 2010 AS PRODUCT OWNER

2. • I check if backlog is • I prepare tools required for • I get the team together at same
session time and place
prepared for the next • I drive discussion
(each) sprint • I arrange meetings
• I track all impediments
• I support Product Owner • I facilitate meetings • I inform about impediments status
• I book room and • I prepare chart & metrics
• I am the first in line in the teleconference meeting • I keep report pages updated
communication channel • I take care of allocation • I track priorities & assignment
• I protect team from disruptions
Backlog Planning Daily scrum
• I invite Product owner • I can add ideas
and team • I can vote
• I arrange place • I will ask chicken to be
silent
• I prepare environment
• I gather ideas
• I drive demo
• I will track responsibilties
• I track comments
Review (Demo) Retrospective
Scrum Cookbook, by Dusan Kocurek, 2010 AS SCRUM MASTER

3. • I can add new stories • I will prepare for meeting • I attend daily meeting
• I responsible for tasks
• I can not remove existing • I re-estimate if necessary • I work based on priorities
stories • I ASK WHY and WHERE IS • I will keep task board updated
• I can not change priority VALUE • I will estimate remaining time
• I will add unplanned tasks
• I estimate business value
• I will self-assign tasks
• I estimate risk and size • I support my colleagues
• I inform about impediments
Backlog Planning Daily scrum
• I prepare demo of my • I share ideas
stories • I vote for ideas
• I do demo • I discuss
• I listen • I ask what was solved
• I discuss comments already
• I wait for acceptation
Review (Demo) Retrospective
Scrum Cookbook, by Dusan Kocurek, 2010
AS TEAM MEMBER

4. Scrum Cookbook, by Dusan Kocurek, 2010