Scrum Cheat Sheet
ADVERTISEMENT
1SCRUM CHEAT SHEET
Roles
Artifacts
Meetings
Scrum Team
Product Backlog - (PB)
Sprint Planning – Day 1 / First Half
Estimating
Team is cross-functional and consists of 5-9 people
List of all desired product features
Product backlog prepared prior to meeting
User Stories
There are no set project roles within the team
List can contain bugs, and non-functional items
First half – Team selects items committing to complete
A very high level definition of what the customer wants
Team defines tasks and assignments
Product Owner responsible for prioritizing
Additional discussion of PB occurs during actual Sprint
the system to do.
Team is self-organizing and self-managing
Items can be added by anyone at anytime
Sprint Planning – Day 1 / Second Half
Each story is captured as a separate item on the
Maintains the Sprint Backlog
Each item should have a business value assigned
Occurs after first half done – PO available for questions
Product Backlog
Conducts the Sprint Review
Maintained by the Product Owner
Team solely responsible for deciding how to build
User stories are NOT dependent on other stories
Product Owner (PO)
Sprint Backlog – (SB)
Tasks created / assigned – Sprint Backlog produced
Story Template:
To-do list (also known as Backlog item) for the Sprint
Daily Scrum
Accountable for product success
“As a <User> I want <function> So that <desired result>
Defines all product features
Created by the Scrum Team
Story Example:
Held every day during a Sprint
Responsible for prioritizing product features
Product Owner has defined as highest priority
As a user, I want to print a recipe so that I can cook it.
Lasts 15 minutes
Maintains the Product Backlog
Burndown Chart – (BC)
Team members report to each other not Scrum Master
Story Points
Insures team working on highest valued features
Asks 3 questions during meeting
Chart showing how much work remaining in a Sprint
A simple way to initially estimate level of effort expected
“What have you done since last daily scrum?”
Scrum Master (SM)
Calculated in hours remaining
to develop
“What will you do before the next daily scrum?”
Holds daily 15 minute team meeting (Daily Scrum)
Maintained by the Scrum Master daily
Story points are a relative measure of feature difficulty
“What obstacles are impeding your work?”
Removes obstacles
Usually scored on a scale of 1-10. 1=very easy through
Release Backlog – (RB)
Opportunity for team members to synchronize their work
Shields the team from external interference
10=very difficult
Same as the Product Backlog. May involve one or
Sprint Review
Maintains the Sprint Burndown Chart
Example:
more sprints dependent on determined Release date
Conducts Sprint Retrospective at the end of a Sprint
“Send to a Friend” Story Points = 2
Team presents “done” code to PO and stakeholders
“DONE”= Potentially Shippable!
Is a facilitator not a manager
“Shopping Cart” Story Points = 9
Functionality not “done” is not shown
Feedback generated - PB maybe reprioritized
Business Value
Process
Scrum Master sets next Sprint Review
FAQ
Each User Story in the Product Backlog should have a
Sprint Retrospective
corresponding business value assigned.
Who decides when a Release happens? At the end
Daily
Scrum
Sprint Review
Attendees – SM and Team. PO is optional
Typically assign (L,M,H) Low, Medium, High
of any given Sprint the PO can initiate a Release.
Who is responsible for managing the teams? The
Questions – What went well and what can be improved?
PO prioritizes Backlog items by highest value
Sprint
SM helps team in discovery – not provide answers
Sprint
teams are responsible for managing themselves.
Backlog
Sprint
Product
Shippable
Estimate Team Capacity
Sprint
Planning
Retrospective
Backlog
Product
What is the length of a task? Tasks should take no
Visibility + Flexibility = Scrum
Capacity = # Teammates (Productive Hrs x Sprint
longer than 16 hours. If longer then the task should be
Days)
Glossary of Terms
broken down further.
Tools
Example – Team size is 4, Productive Hrs are 5, Sprint
Who manages obstacles? Primary responsibility is
Time Box - A period of time to finish a task. The end
length is 30 days.
Task Board
date is set and can not be changed
on the Scrum Master. However, teams must learn to
Capacity = 4 (5 x30) = 600 hours
resolve their own issues. If not able then escalated to
Chickens – People that are not committed to the project
White Board containing teams Sprint goals, backlog items,
NOTE: Account for vacation time during the Sprint!
SM.
and are not accountable for deliverables
tasks, tasks in progress, “DONE” items and the daily Sprint
Velocity
Pigs – People who are accountable for the project’s
What are two of the biggest challenges in Scrum?
Burndown chart.
Teams not self-managing, Scrum Master
success
Scrum meeting best held around task board
The rate at which team converts items to “DONE” in a
managing not leading.
Single Wringable Neck – This is the Product Owner!
single Sprint – Usually calculated in Story Points.
Visible to everyone
ADVERTISEMENT
0 votes
Related Articles
Related forms
Related Categories
Parent category: Education