Scrum Cheat Sheet

https://ini.tl/scrum

Product Owner Product Backlog

(Emerging, Prioritized Contents: Can be anything (bug reports, demands, etc.) but preferrable (or converted to) user
makes/updates Req uirements) stories (As a <end user role>, I w ant <functionality>, so that <benefit>).
Product Backlog
Duration: 2 hours*
Attendees: Product Owner, Team, ScrumMaster
Activities: Team selects those Product Backlog items that it believes it can commit to turning
into an increment of potentially shippable product functionality, Product Owner is
responsible for what product backlog items are in the Sprint. The team is responsible for
Sprint Planning I determining how much of the Product Backlog that the Product Owner wants will attempt to
Release gets
Burndown upd ated
(What?) do. At second sprint the ScrumMaster can update the release burndown using the previous
Selecting Product Backlog velocity.
Items
Conditions: The product backlog must have an estimation coverage of 80%, if not (or at first
sprint) the team first estimates all users stories in story points (planning poker).
There are no chickens as observers. The product backlog must be prepared prior to this
meeting. When the Product Owner or Product Backlog is not there the ScrumMaster will
stand in and create the Product Backlog

Duration: 2 hours*
Sprint Backlog Sprint Planning Attendees: Team, ScrumMaster, Product Owner (Optional but available)
(Tasks, Task Activities: The team acting solely on its ow n will figure out how it will turn the selected
Estimates,
results II product backlog item into an increment of potentially shippable product functionality .
in
Assignments) (How?) Generate a list of tasks, task estimates in hours (planning poker), assignments.
Prepare Sprint Backlog Conditions: Occurs immediately after Sprint Planning I. Everyone outside the team is only
allowed to observe or answer questions.
Duration: 14 days*
Activities: The team commits to the Sprint Backlog so that it gets ‘done’. The team can seek
Scrumb oard outside advice, help, info and support during the sprint. Team members have two
with Sprint gets administrative responsibilities during the sprint: 1) attending the daily scrum meeting; 2) keep
Bu rn down updated
Chart Sprinting the Sprint Backlog/Scrumboard up-to-date.
Conditions: Everyone outside the team is only allowed to observe or answ er questions . The
Sprint Backlog is frozen during the sprint.The team is selfmanaging. No one is allowed to
change the Sprint Backlog. No one can provide advice, instructions, commentary, or direction
to the team during the Sprint.
Duration: 15 minutes
Attendees: Team, ScrumMaster
Activities: Each Team m ember answers three questions:
1) What have you done since the last DSM?
yes
2) What will you do between now and the next DSM?
3) What impediments do you have from working effectively?
The ScrumMaster tries to take aw ay the impediments.
Daily Scrum
Conditions: All Team members are required to attend (absent mem bers by telephone, or
Meeting another member knowing the status). Only one person talks at a time, everyone else listens,
there are no side conversations. No discussion of issues. Chickens are not allowed to talk or
make their presence obtrusive. When there are too many chickens the Scrum Master can limit
attendance. Chickens are not allowed to talk with Team members after the meeting for
clarification, instructions or advice.
Still Team members or chickens who can not confirm to these conditions will be excluded from the
Inside Sprint meeting or team.
Timebox?
Duration: 2 hours*
Attendees: Team, ScrumMaster, Product Owner, Stakeholders (Optional)
no
Activities: A team member presenting the sprint goal, the product backlog items commited to,
and the product backlog completed. Then the team presents to the Product Owner and
stakeholders functionality that is done (according to the definition of ‘done’). Stakeholders are
Sprint Review polled, one by one to get their impressions. The Product Owner discusses the potential
Meeting rearrangement of the Product Backlog. Stakeholders are free to voice any comments ,
observations, criticisms. Stakeholders can identify functionality that was not thought of or
delivered and request it to be placed on the Product Backlog and request prioritization.
Conditions: The team should not spend more than 1 hour preparing for the sprint review. Only
‘done’ functionality can be shown to avoid confusion. Functionality should be presented on the
environment closest (most similar) to production.

Duration: 1.5 hours*

Attendees: Team, ScrumMaster, Product Owner (Optional)
Sprint Activities: Each Team m ember must answer two questions:
Retrospective 1) What went well during last Sprint?
Meeting 2) What could be improved in the next Sprint?
The ScrumMaster will take notes of answers. Talk about improvements of the Scrum process.
The ScrumMaster will try to facilitate this.

*This cheat sheet is based on a sprint duration of 2 weeks. Using a different duration? Adjust duration of meetings accordingly
 Scrum Cheat Sheet
https://ini.tl/scrum

Good Practise Scrum

1. Full-Time Product Owner (with Expertise and Authority) Identified
2. Product Owner Works With Team and All Other Stakeholders
3. Product Backlog Created and Managed by Product Owner
4. Daily Scrum Meeting with 3 Questions (Completed? Will Complete? Obstacles?)
5. Daily Scrum Meeting Same Place and Time and Less Than 15 Minutes
6. Regular Sprint Length (no more than 30 days)
7. Sprint Planning Meeting to Create Sprint Backlog of Estimated Tasks
8. Sprint Burndown Chart
9. Team Room with All Needed Equipment and Supplies
10. Retrospective Meeting for Process Improvements
11. Definition of "Done"
12. Commitment Velocity Calculated (from Sprint Backlog Estimates)
13. Team Size 7 +/-2, Maximum of 12
14. Cross-Functional Team Including ScrumMaster and Product Owner
15. Team Self-Organization - Team Members Volunteer for Tasks
16. ScrumMaster Tracking and Removing Obstacles
17. Team Safety - No Interruptions to Team's Work During Sprints
18. No "Break" Between Sprints
19. Sustainable Pace - Timebox Effort, Not Just Schedule
20. Quality is Not Negotiable - Defects Go on Top of Product Backlog