1. WWW.AGILE42.COM
Scrum Cheat Sheet by agile42
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 Team listed in the Product Backlog. It is an
project (Stakeholder) and he is thinks they have enough Stories to start always changing, dynamically prioritized
responsible for the final product. the Sprint, they begin breaking it down in list of requirements ordered by Business
Tasks to fill the Sprint Backlog (normally 3 Value. Requirements are broken down
• elicit product requirements to 4 days of work, than inspect & adapt). into User Stories by the PO.
• manage the Product Backlog Prioritize the requirements by
Timebox: 4 hours
• manage the release plan Owner: Product Owner playing the Business Value game.
• manage the Return on Investment Participants: Team, Scrum Master Buy these at www.agile42.com
Scrum Master Daily Scrum Burndown Chart
Owns the Scrum process Inspect and Adapt the progress Displays the remaining work
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 adaptation as necessary. between work remaining at any point in
Master is not part of the Team. Timebox: 15-20 minutes time and the progress of the Team(s).
• 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
Development Team Sprint Review Sprint Backlog
Owns the software Demonstrate the achievements List of Tasks to fulfill the Sprint Goal
The team figures out how to turn the The team demonstrate the PO the result - The Sprint Backlog contains all the
Product Backlog into an increment of on the developed product - of the Sprint. committed User Stories for the current
functionality within a Sprint. Each team The PO can accept or reject features Sprint broken down into Tasks by the
member is jointly responsible for the depending on the agreed acceptance Team. All items on the Sprint Backlog
success of each iteration and of the criteria. should be developed, tested, documented
project as a whole. and integrated in order to fulfill the Sprint
Goal.
Timebox: 4 hours
• software quality Owner: Team
• technical implementation of User Stories Estimate Story complexity by playing
Participants: Scrum Master, Product
• delivery of a “potentially shippable” Planning Poker.
Owner, optionally the PO can invite
product increment at every Sprint Buy these at www.agile42.com
other Stakeholders
________________________ Retrospective _________________________
Requirements Maintain the good, get rid of the bad Potentially Shippable Product
Make SMART Requirements: Simple,
Measurable, Achievable, Realistic, At the end of a Sprint, the Team Scrum requires at the end of each Sprint
Traceable. evaluates the finished Sprint. They that the product is potential shippable to
capture positive ways as a best practice, the customer. That means the increment
User Stories identify challenges and develop is:
INVEST in User Stores: Independent, strategies for improvements. • thoroughly tested and stable
Negotiable, Valuable, Estimable, Small, • well-structured
Testable. Timebox: 3 hours • well-written code
Owner: Scrum Master • user operation of the functionality is
Tasks documented
Participants: Team, (Product Owner)
Make sure a Task is TECH. Time boxed,
Everybody (can pick it up), Complete and
Human-readable.
agile42 - www.agile42.com - all rights reserved © 2009