SCRUM CHEAT SHEET

• 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.

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

• 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.

• 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.

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

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

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

• Product backlog prepared prior to meeting.
• First half – Team selects items committing to complete.
• Additional discussion of PB occurs during actual Sprint.

• Occurs after first half is done – PO available for questions.
• Team solely responsible for deciding how to build.
• Tasks created / assigned – Sprint Backlog produced.

• Held every day during a Sprint.
• Lasts 15 minutes.
• Team members report to each other, not Scrum Master.
• Asks three questions during meeting.

Opportunity for team members to synchronize their work.

• Team presents “done” code to PO and stakeholders.
• Functionality not “done” is not shown.
• Feedback generated - PB may be reprioritized.
• Scrum Master sets next Sprint Review.

• Attendees – SM and Team. PO is optional.
• Questions – What went well and what can be improved?
• SM helps team in discovery – not provide answers.

• White Board containing team's Sprint goals, backlog items, tasks, tasks in progress, “DONE” items and the daily Sprint Burndown chart.
• Scrum meeting best held around task board.
• Visible to everyone.

A very high level definition of what the customer wants the system to do.

• Each story is captured as a separate item on the Product Backlog.
• User stories are NOT dependent on other stories.

Story Template

Story Example

A simple way to initially estimate level of effort expected to develop.

• Story points are a relative measure of feature difficulty.
• Usually scored on a scale of 1-10.
• 1 = very easy through 10 = very difficult.

Examples

Example

Team size is 4, Productive Hrs are 5, Sprint length is 30 days.

• Each User Story in the Product Backlog should have a corresponding business value assigned.
• Typically assign (L, M, H) — Low, Medium, High.
• PO prioritizes Backlog items by highest value.