Scrum Cheat Sheet

Roles Meetings Artifacts Glossary

Product Owner (PO): Responsible for the product Sprint Planning Part I: Define “What” to do Product Backlog: List of desired product Timebox: A period of time of fixed length
success features which cannot be exceeded.
• PO presents top priority Product Backlog items
• Envisions the product • Team selects the amount of Backlog for the • Is Detailed, Emergent, Estimated, Prioritized
• Is the only one responsible for the Product Backlog upcoming Sprint (DEEP) Scrum Team: The Team, the PO and the
(items and prioritization) • Acceptance criteria are negotiated and • More details on higher priority backlog ScrumMaster form the Scrum Team.
• Is responsible for the product ‘s profitability (ROI) clarified items
• Decides on release date and content • Sprint Goal is defined • Maintained by the Product Owner but
• Accepts or rejects work results anyone can contribute Definition of “Done” (DoD): List of
• Collaborates with both the team and stakeholders Sprint Planning Part II: Define “How” to do • One list per product development activities required to
• Team participates while PO’s available • Needs to be groomed every Sprint consider an increment of functionality as
Team: Responsible for delivering product • Team breaks items into tasks to form the Sprint Backlog: Tasks to turn Product “Done”.
functionalities Sprint Backlog Backlog items into working product
• Involves detailed design functionality Sprint Taskboard: A board containing the
• Self-organizing • Team makes commitment for the Sprint
• Cross-functional with no roles • The selected Product Backlog items for the team’s Sprint goals, Sprint Backlog and
• Seven plus or minus two Daily Scrum: Inspection and adaptation the Sprint Burndown chart. Physical white
sprint do not change during the sprint
• Responsible for meeting their commitments meeting for the Sprint • Made and maintained by the team boards are recommended.
• Authority to do whatever is needed to meet • 15 minute Daily status meeting throughout the Sprint
commitments • Same place and time every day • Any team member can add, delete or change Velocity: The rate at which team converts
• Three questions for everyone a task the Sprint Backlog
• What have you completed since last meeting? • Team members sign up for tasks, they aren’t items to “DONE” in a single Sprint. It is
• What will you complete before next meeting? assigned usually calculated in Story Points.
• What is in your way? • The size of a task should be less than 1 day
• Team updates the Sprint backlog and Sprint • Estimated work remaining is updated daily User Story: a short description of a
ScrumMaster: Responsible for the success of Scrum Burndown chart Sprint Burndown chart: Shows remaining behavior of the system in the point of
• Open meeting for all, but only Scrum Team
• Enforces the Scrum Rules work in a Sprint view of the user.
members can talk
• Facilitates all the Scrum meetings • Calculated with the number of remaining User Story template:
• Shields the team from external interference tasks or story points As a <User>, I can <function> so that
• Leads the team to be self-organizing and to Sprint Review: Inspection and adaptation • Updated daily by the team <desired result>.
continuously improve meeting about the product Release Burndown Chart: Shows remaining
• Coaches the PO on his role • Team presents the “Done” work and
• Serves the team and PO work in a release Story Points: a relative measure of the
“Undone” work
• Removes obstacles • Get feedback from the Product Owner and • Calculated in story points size of the user stories. Can have different
• Is a change agent Stakeholders • Maintained by product owner scales, typically Fibonacci sequence as in
Scrum flow: • Update Product Backlog and release • Updated every Sprint Planning Poker.
Burndown chart
Sprint Retrospective: Inspection and The 3 pillars of Scrum: The 5 Scrum values:
adaptation meeting about the process Commitment
• Scrum Team inspects the last sprint regarding Transparency Focus
people, relationships, processes and tools
• Scrum Team identifies possible improvements Inspection Openness
and agrees on the measures for next Sprint
• Scrum Team may update its own working Adaptation Respect
agreement Courage