Scribd
Upload
834 views

Scrum Cheat Sheet

Product Owner Owns the Product Backlog the product Owner represents the interests of everyone with a stake in the project. Scrum Master Owns the Scrum process The Scrum Master ensures everybody plays by the rules and removes impediments for the team. Team members are jointly responsible for the success of each iteration and of the project as a whole.

Uploaded by

hohingday
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
834 views

Scrum Cheat Sheet

Product Owner Owns the Product Backlog the product Owner represents the interests of everyone with a stake in the project. Scrum Master Owns the Scrum process The Scrum Master ensures everybody plays by the rules and removes impediments for the team. Team members are jointly responsible for the success of each iteration and of the project as a whole.

Uploaded by

hohingday
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Scrum Cheat Sheet

Product Owner Sprint Planning Product Backlog


Owns the Product Backlog Commit the deliverable(s) to the PO Dynamic prioritized list of requirements

The Product Owner represents the Two part meeting. First, the PO presents The requirements for the product are
interests of everyone with a stake in the the User Stories. Second, when the listed in the Product Backlog. It is an
project (Stakeholder) and he is Team thinks they have enough Stories to always changing, dynamically prioritized
responsible for the final product. start the Sprint, they begin breaking it list of requirements ordered by Business
down in Tasks to fill the Sprint Backlog. Value. Requirements are broken down
• elicit product requirements into User Stories by the PO.
• manage the Product Backlog Timebox: 4 hours
• manage the release plan Owner: Product Owner Prioritize the requirements by
• manage the Return on Investment Participants: Team, Scrum Master playing the Business Value game.

Buy these at www.agile42.com

Scrum Master Daily Scrum Burndown Chart


Owns the Scrum process Inspect and Adapt the progress Estimated remaining time of the Sprint

The Scrum Master is responsible for the In this standup meeting the Team daily The Burndown chart shows the amount of
Scrum process.He ensures everybody inspects their progress in relation to the work remaining per Sprint. It is a very
plays by the rules. He also removes Planning by using the Burndown Chart, useful way of visualizing the correlation
impediments for the Team. The Scrum and makes adjustments as necessary. between work remaining at any point in
Master is not part of the Team. time and the progress of the Team(s).
Timebox: 15 minutes
• manage the Scrum process Owner: Scrum Master Use a tool such as Agilo to automatically
• remove impediments Participants: Team, all interested create the Burndown Chart.
• facilitate communication parties may silently attend.
Learn more at www.agile42.com

Team Member Retrospective Sprint Backlog


Owns the software Maintain the good, get rid of the bad List of committed User Stories

The team figures out how to turn the At the end of a Sprint, the Team The Sprint Backlog contains all the
Product Backlog into an increment of evaluates the finished Sprint. They committed User Stories for the current
functionality within a Sprint. Each team capture positive ways as a best practice, Sprint broken down into Tasks by the
member is jointly responsible for the identify challenges and develop Team. All items on the Sprint Backlog
success of each iteration and of the strategies for improvements. should be developed, tested, documented
project as a whole. and integrated to fullfil the commitment.
Timebox: 2 hours
• software quality Owner: Scrum Master Estimate Story complexity
• technical implimentation of User Stories Participants: Team, Product Owner, by playing Planning Poker.
• delivery of functional software increment optionally the PO can invite
• to organize themselves Stakeholders Buy these at www.agile42.com

Requirements User Stories Tasks


Make SMART Requirements: Simple, INVEST in User Stores: Independant, Make sure a Task is TECH. Time boxed,
Measurable, Achievable, Realistic, Negotiable, Valuable, Estimatable, Small, Everybody (can pick it up), Complete and
Traceable. Traceable. Human-readable.

agile42 - http://www.agile42.com - all rights reserved © 2008

You might also like