Scrum Cheat Sheet

8 Mar
2010

I’ve been learning a bit about the Scrum methodology lately (both the workplace and at uni), and I came across this nice looking Scrum Cheat Sheet. It is a few years old now, but it highlights the major roles, artifacts, meetings, etc.

You can download a copy of at Scribd. If the link doesn’t work or you can’t download it let me know and I’ll see if I can e-mail it to you or post it up on here. It places all the information on a nice landscape page!

I’ve copied some of the text below to give you an idea of how it is set out.

Roles

Scrum Team

  • Team is cross-functional and consists of 5-9 people
  • There are no set project roles within the team
  • Team defines tasks and assignments
  • Team is self-organizing and self-managing
  • Maintains the Sprint Backlog
  • Conducts the Sprint Review

Product Owner (PO)

  • Accountable for product success
  • Defines all product features
  • Responsible for prioritizing product features
  • Maintains the Product Backlog
  • Insures team working on highest valued features

Scrum Master (SM)

  • Holds daily 15 minute team meeting (Daily Scrum)
  • Removes obstacles
  • Shields the team from external interference
  • Maintains the Sprint Burndown Chart
  • Conducts Sprint Retrospective at the end of a Sprint
  • Is a facilitator not a manager

Artifacts

Product Backlog – (PB)

  • List of all desired product features
  • List can contain bugs, and non-functional items
  • Product Owner responsible for prioritizing
  • Items can be added by anyone at anytime
  • Each item should have a business value assigned
  • Maintained by the Product Owner

Sprint Backlog – (SB)

  • To-do list (also known as Backlog item) for the Sprint
  • Created by the Scrum Team
  • Product Owner has defined as highest priority

Burndown Chart – (BC)

  • Chart showing how much work remaining in a Sprint
  • Calculated in hours remaining
  • Maintained by the Scrum Master daily

Release Backlog – (RB)

  • Same as the Product Backlog. May involve one or more sprints dependent on determined Release date

Update: For some reason or another people are have problem getting to the Scrum Cheat Sheet. I would recommend you try and get it from the above link but for those who can’t I’ve decided to upload it here –> Scrum Cheat Sheet <–

Comment Form

top