SlideShare a Scribd company logo
Artifacts
To-do list (also known as Backlog item) for the Sprint
Created by the Scrum Team
Product Owner has defined as highest priority
Sprint Backlog – (SB)
Chart showing how much work remaining in a Sprint
Calculated in hours remaining
Maintained by the Scrum Master daily
Burndown Chart – (BC)
Same as the Product Backlog. May involve one or
more sprints dependent on determined Release date
Release Backlog – (RB)
Meetings
Product backlog prepared prior to meeting
First half – Team selects items committing to complete
Additional discussion of PB occurs during actual Sprint
Sprint Planning – Day 1 / First Half
Team presents “done” code to PO and stakeholders
Functionality not “done” is not shown
Feedback generated - PB maybe reprioritized
Scrum Master sets next Sprint Review
Sprint Review
Occurs after first half done – PO available for questions
Team solely responsible for deciding how to build
Tasks created / assigned – Sprint Backlog produced
Sprint Planning – Day 1 / Second Half
Held every day during a Sprint
Lasts 15 minutes
Team members report to each other not Scrum Master
Asks 3 questions during meeting
“What have you done since last daily scrum?”
“What will you do before the next daily scrum?”
“What obstacles are impeding your work?”
Opportunity for team members to synchronize their work
Daily Scrum
Estimating
“DONE”= Potentially Shippable!
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
Product Backlog - (PB)
SCRUM CHEAT SHEET
Attendees – SM and Team. PO is optional
Questions – What went well and what can be improved?
SM helps team in discovery – not provide answers
Sprint Retrospective
Roles
Accountable for product success
Defines all product features
Responsible for prioritizing product features
Maintains the Product Backlog
Insures team working on highest valued features
Product Owner (PO)
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
Scrum Master (SM)
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
Scrum Team
FAQ
Who decides when a Release happens? At the end
of any given Sprint the PO can initiate a Release.
Who is responsible for managing the teams? The
teams are responsible for managing themselves.
What is the length of a task? Tasks should take no
longer than 16 hours. If longer then the task should be
broken down further.
Who manages obstacles? Primary responsibility is
on the Scrum Master. However, teams must learn to
resolve their own issues. If not able then escalated to
SM.
What are two of the biggest challenges in Scrum?
Teams not self-managing, Scrum Master
managing not leading.
White Board containing teams 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
Task Board
Tools
Process
Shippable
Product
Sprint Review
Sprint
Daily
Scrum
Sprint
BacklogProduct
Backlog
Sprint
Planning
Sprint
Retrospective
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:
“As a <User> I want <function> So that <desired result>
Story Example:
As a user, I want to print a recipe so that I can cook it.
User Stories
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
Example:
“Send to a Friend” Story Points = 2
“Shopping Cart” Story Points = 9
Story Points
Capacity = # Teammates (Productive Hrs x Sprint
Days)
Example – Team size is 4, Productive Hrs are 5, Sprint
length is 30 days.
Capacity = 4 (5 x30) = 600 hours
NOTE: Account for vacation time during the Sprint!
Estimate Team Capacity
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
Business Value
Glossary of Terms
Time Box - A period of time to finish a task. The end
date is set and can not be changed
Chickens – People that are not committed to the project
and are not accountable for deliverables
Pigs – People who are accountable for the project’s
success
Single Wringable Neck – This is the Product Owner!
The rate at which team converts items to “DONE” in a
single Sprint – Usually calculated in Story Points.
Velocity
Visibility + Flexibility = Scrum

More Related Content

What's hot

Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
Sriram Srinivasan
 
Scrum in 15 Minutes
Scrum in 15 MinutesScrum in 15 Minutes
Scrum in 15 Minutes
Serge Rehem
 
Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018
pmengal
 
Agile Scrum Estimation
Agile   Scrum EstimationAgile   Scrum Estimation
Agile Scrum Estimation
Prasad Prabhakaran
 
Scrum refinement
Scrum refinementScrum refinement
Scrum refinement
Vincenzo Favara
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.
SlideTeam.net
 
Scrum
ScrumScrum
Scrum Cheat Sheet
Scrum Cheat SheetScrum Cheat Sheet
Scrum Cheat Sheet
Edwin Ritter
 
2017 Scrum by Picture
2017 Scrum by Picture2017 Scrum by Picture
2017 Scrum by Picture
Pawel Lewinski
 
Agile scrum fundamentals
Agile scrum fundamentalsAgile scrum fundamentals
Agile scrum fundamentals
Deniz Gungor
 
E0 dd1d scrum-cheat-sheet
E0 dd1d scrum-cheat-sheetE0 dd1d scrum-cheat-sheet
E0 dd1d scrum-cheat-sheet
Rama Devi Drakshpalli
 
Agile scrum training
Agile scrum trainingAgile scrum training
Scrum 101
Scrum 101Scrum 101
Scrum 101
beLithe
 
Story Points Estimation And Planning Poker
Story Points Estimation And Planning PokerStory Points Estimation And Planning Poker
Story Points Estimation And Planning Poker
Daniel Toader
 
Agile Introduction - Scrum Framework
Agile Introduction - Scrum FrameworkAgile Introduction - Scrum Framework
Agile Introduction - Scrum Framework
Kshitij Yelkar MBA/PMP/CSM/ICP-ACC
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training Process
Clarion Marketing
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
Srikanth Shreenivas
 
Understanding Scrum in 30 Minutes
Understanding Scrum in 30 MinutesUnderstanding Scrum in 30 Minutes
Understanding Scrum in 30 Minutes
Altaf Najvani
 
The Essence of Sprint Planning : Presented by Sprint Planning
The Essence of Sprint Planning : Presented by Sprint PlanningThe Essence of Sprint Planning : Presented by Sprint Planning
The Essence of Sprint Planning : Presented by Sprint Planning
oGuild .
 
Scrum cheat sheet
Scrum cheat sheetScrum cheat sheet
Scrum cheat sheet
Christopher Daily
 

What's hot (20)

Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Scrum in 15 Minutes
Scrum in 15 MinutesScrum in 15 Minutes
Scrum in 15 Minutes
 
Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018
 
Agile Scrum Estimation
Agile   Scrum EstimationAgile   Scrum Estimation
Agile Scrum Estimation
 
Scrum refinement
Scrum refinementScrum refinement
Scrum refinement
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.
 
Scrum
ScrumScrum
Scrum
 
Scrum Cheat Sheet
Scrum Cheat SheetScrum Cheat Sheet
Scrum Cheat Sheet
 
2017 Scrum by Picture
2017 Scrum by Picture2017 Scrum by Picture
2017 Scrum by Picture
 
Agile scrum fundamentals
Agile scrum fundamentalsAgile scrum fundamentals
Agile scrum fundamentals
 
E0 dd1d scrum-cheat-sheet
E0 dd1d scrum-cheat-sheetE0 dd1d scrum-cheat-sheet
E0 dd1d scrum-cheat-sheet
 
Agile scrum training
Agile scrum trainingAgile scrum training
Agile scrum training
 
Scrum 101
Scrum 101Scrum 101
Scrum 101
 
Story Points Estimation And Planning Poker
Story Points Estimation And Planning PokerStory Points Estimation And Planning Poker
Story Points Estimation And Planning Poker
 
Agile Introduction - Scrum Framework
Agile Introduction - Scrum FrameworkAgile Introduction - Scrum Framework
Agile Introduction - Scrum Framework
 
Agile Scrum Training Process
Agile Scrum Training ProcessAgile Scrum Training Process
Agile Scrum Training Process
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
 
Understanding Scrum in 30 Minutes
Understanding Scrum in 30 MinutesUnderstanding Scrum in 30 Minutes
Understanding Scrum in 30 Minutes
 
The Essence of Sprint Planning : Presented by Sprint Planning
The Essence of Sprint Planning : Presented by Sprint PlanningThe Essence of Sprint Planning : Presented by Sprint Planning
The Essence of Sprint Planning : Presented by Sprint Planning
 
Scrum cheat sheet
Scrum cheat sheetScrum cheat sheet
Scrum cheat sheet
 

Viewers also liked

Agile Checklist
Agile ChecklistAgile Checklist
Agile Checklist
Joshua A. Jack
 
Facilitation Foundations - A Guide to Effective Agile Meetings
Facilitation Foundations - A Guide to Effective Agile MeetingsFacilitation Foundations - A Guide to Effective Agile Meetings
Facilitation Foundations - A Guide to Effective Agile Meetings
AgileDad
 
ScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn Tuấn
ScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn TuấnScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn Tuấn
ScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn Tuấn
Vu Hung Nguyen
 
ScrumDay Vietnam 2012 - Scrum tu chien hao VNext - Trung
ScrumDay Vietnam 2012 - Scrum tu chien hao VNext - TrungScrumDay Vietnam 2012 - Scrum tu chien hao VNext - Trung
ScrumDay Vietnam 2012 - Scrum tu chien hao VNext - Trung
DUONG Trong Tan
 
«Почему SCRUM не работает?» или «SCRUM: как правильно?»
«Почему SCRUM не работает?» или «SCRUM: как правильно?»«Почему SCRUM не работает?» или «SCRUM: как правильно?»
«Почему SCRUM не работает?» или «SCRUM: как правильно?»
ak-itconsulting.com
 
Beginning SCRUM for Startups
Beginning SCRUM for StartupsBeginning SCRUM for Startups
Beginning SCRUM for Startups
Pradeep Sethi
 
Scrum Checklist
Scrum ChecklistScrum Checklist
Scrum Checklist
Demetrius Nunes
 
Good-vs-great-agile-teams
Good-vs-great-agile-teamsGood-vs-great-agile-teams
Good-vs-great-agile-teams
Dave Sharrock
 
ScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh Cường
ScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh CườngScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh Cường
ScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh Cường
Vu Hung Nguyen
 
ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...
ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...
ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...
Vu Hung Nguyen
 
ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...
ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...
ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...
Vu Hung Nguyen
 
Phương pháp phát triển phần mềm: Truyền thống và Agile
Phương pháp phát triển phần mềm: Truyền thống và AgilePhương pháp phát triển phần mềm: Truyền thống và Agile
Phương pháp phát triển phần mềm: Truyền thống và Agile
Vu Hung Nguyen
 
A brief introduction to agile duong trong tan 2014-06
A brief introduction to agile  duong trong tan 2014-06A brief introduction to agile  duong trong tan 2014-06
A brief introduction to agile duong trong tan 2014-06
Vu Hung Nguyen
 
SCRUM on a page - by Axon Active Vietnam
SCRUM on a page - by Axon Active VietnamSCRUM on a page - by Axon Active Vietnam
SCRUM on a page - by Axon Active Vietnam
Axon Active Vietnam
 
Ultrasound artifacts
Ultrasound artifactsUltrasound artifacts
Ultrasound artifacts
ansaripv
 
Software Development Model - Waterfall, RAD & Agile
Software Development Model - Waterfall, RAD & AgileSoftware Development Model - Waterfall, RAD & Agile
Software Development Model - Waterfall, RAD & Agile
Fakrudin Abu Bakar
 
Release Management: Successful Software Releases Start with a Plan
Release Management: Successful Software Releases Start with a PlanRelease Management: Successful Software Releases Start with a Plan
Release Management: Successful Software Releases Start with a Plan
connielharper
 

Viewers also liked (17)

Agile Checklist
Agile ChecklistAgile Checklist
Agile Checklist
 
Facilitation Foundations - A Guide to Effective Agile Meetings
Facilitation Foundations - A Guide to Effective Agile MeetingsFacilitation Foundations - A Guide to Effective Agile Meetings
Facilitation Foundations - A Guide to Effective Agile Meetings
 
ScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn Tuấn
ScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn TuấnScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn Tuấn
ScrumDay Vietnam 2013: Building Reliable Agile Teams - Lê Văn Tuấn
 
ScrumDay Vietnam 2012 - Scrum tu chien hao VNext - Trung
ScrumDay Vietnam 2012 - Scrum tu chien hao VNext - TrungScrumDay Vietnam 2012 - Scrum tu chien hao VNext - Trung
ScrumDay Vietnam 2012 - Scrum tu chien hao VNext - Trung
 
«Почему SCRUM не работает?» или «SCRUM: как правильно?»
«Почему SCRUM не работает?» или «SCRUM: как правильно?»«Почему SCRUM не работает?» или «SCRUM: как правильно?»
«Почему SCRUM не работает?» или «SCRUM: как правильно?»
 
Beginning SCRUM for Startups
Beginning SCRUM for StartupsBeginning SCRUM for Startups
Beginning SCRUM for Startups
 
Scrum Checklist
Scrum ChecklistScrum Checklist
Scrum Checklist
 
Good-vs-great-agile-teams
Good-vs-great-agile-teamsGood-vs-great-agile-teams
Good-vs-great-agile-teams
 
ScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh Cường
ScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh CườngScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh Cường
ScrumDay Vietnam 2013: PMBOK là Waterfall hay Agile? - Phùng Thanh Cường
 
ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...
ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...
ScrumDay Vietnam 2013: Phương pháp luận phần mềm - Truyền thống và Agile - Ng...
 
ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...
ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...
ScrumDay Vietnam 2013: Ứng dụng Jira trong Phát triển Phần mềm Linh hoạt - Ng...
 
Phương pháp phát triển phần mềm: Truyền thống và Agile
Phương pháp phát triển phần mềm: Truyền thống và AgilePhương pháp phát triển phần mềm: Truyền thống và Agile
Phương pháp phát triển phần mềm: Truyền thống và Agile
 
A brief introduction to agile duong trong tan 2014-06
A brief introduction to agile  duong trong tan 2014-06A brief introduction to agile  duong trong tan 2014-06
A brief introduction to agile duong trong tan 2014-06
 
SCRUM on a page - by Axon Active Vietnam
SCRUM on a page - by Axon Active VietnamSCRUM on a page - by Axon Active Vietnam
SCRUM on a page - by Axon Active Vietnam
 
Ultrasound artifacts
Ultrasound artifactsUltrasound artifacts
Ultrasound artifacts
 
Software Development Model - Waterfall, RAD & Agile
Software Development Model - Waterfall, RAD & AgileSoftware Development Model - Waterfall, RAD & Agile
Software Development Model - Waterfall, RAD & Agile
 
Release Management: Successful Software Releases Start with a Plan
Release Management: Successful Software Releases Start with a PlanRelease Management: Successful Software Releases Start with a Plan
Release Management: Successful Software Releases Start with a Plan
 

Similar to Scrum cheatsheet

Kupdf.net scrum cheat-sheet
Kupdf.net scrum cheat-sheetKupdf.net scrum cheat-sheet
Kupdf.net scrum cheat-sheet
Vinu Gopal
 
Scrum
ScrumScrum
Scrum
breccan
 
Agile processes scrum
Agile processes scrumAgile processes scrum
Agile processes scrum
Pruthviraj Yerram
 
Scrum framework
Scrum frameworkScrum framework
Scrum framework
Rashmi Pathak
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
Deepak Mittal
 
Scrum Primer
Scrum PrimerScrum Primer
Scrum Primer
davelucey
 
Scrum
ScrumScrum
Scrum
Akhil Prem
 
Scrum: Waterfall Into Scrum
Scrum: Waterfall Into ScrumScrum: Waterfall Into Scrum
Scrum: Waterfall Into Scrum
Chad Holdorf
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
vineet
 
Scrum Reference Card
Scrum Reference CardScrum Reference Card
Scrum Reference Card
enderturan
 
Introduction to agile
Introduction to agileIntroduction to agile
Introduction to agile
Sandipp Vijj, Digital Disruptor
 
Agile Scrum Methodology
Agile Scrum MethodologyAgile Scrum Methodology
Agile Scrum Methodology
Rajeev Misra
 
Scrum
ScrumScrum
Scrum
gargiz
 
Scrum referencecard
Scrum referencecardScrum referencecard
Scrum referencecard
Suresh Kumar
 
Scrum Overview
Scrum OverviewScrum Overview
Scrum Overview
sourav_techjini
 
Waterfall vs agile approach scrum framework and best practices in software d...
Waterfall vs agile approach  scrum framework and best practices in software d...Waterfall vs agile approach  scrum framework and best practices in software d...
Waterfall vs agile approach scrum framework and best practices in software d...
Tayfun Bilsel
 
Scrum 101+
Scrum 101+Scrum 101+
Succeed with Scrum - Part 1
Succeed with Scrum - Part 1Succeed with Scrum - Part 1
Succeed with Scrum - Part 1
Satisha K Venkataramaiah
 
Agile scrum induction
Agile scrum inductionAgile scrum induction
Agile scrum induction
Priyank Pathak
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
MujeebMohammed18
 

Similar to Scrum cheatsheet (20)

Kupdf.net scrum cheat-sheet
Kupdf.net scrum cheat-sheetKupdf.net scrum cheat-sheet
Kupdf.net scrum cheat-sheet
 
Scrum
ScrumScrum
Scrum
 
Agile processes scrum
Agile processes scrumAgile processes scrum
Agile processes scrum
 
Scrum framework
Scrum frameworkScrum framework
Scrum framework
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
 
Scrum Primer
Scrum PrimerScrum Primer
Scrum Primer
 
Scrum
ScrumScrum
Scrum
 
Scrum: Waterfall Into Scrum
Scrum: Waterfall Into ScrumScrum: Waterfall Into Scrum
Scrum: Waterfall Into Scrum
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
 
Scrum Reference Card
Scrum Reference CardScrum Reference Card
Scrum Reference Card
 
Introduction to agile
Introduction to agileIntroduction to agile
Introduction to agile
 
Agile Scrum Methodology
Agile Scrum MethodologyAgile Scrum Methodology
Agile Scrum Methodology
 
Scrum
ScrumScrum
Scrum
 
Scrum referencecard
Scrum referencecardScrum referencecard
Scrum referencecard
 
Scrum Overview
Scrum OverviewScrum Overview
Scrum Overview
 
Waterfall vs agile approach scrum framework and best practices in software d...
Waterfall vs agile approach  scrum framework and best practices in software d...Waterfall vs agile approach  scrum framework and best practices in software d...
Waterfall vs agile approach scrum framework and best practices in software d...
 
Scrum 101+
Scrum 101+Scrum 101+
Scrum 101+
 
Succeed with Scrum - Part 1
Succeed with Scrum - Part 1Succeed with Scrum - Part 1
Succeed with Scrum - Part 1
 
Agile scrum induction
Agile scrum inductionAgile scrum induction
Agile scrum induction
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 

Scrum cheatsheet

  • 1. Artifacts To-do list (also known as Backlog item) for the Sprint Created by the Scrum Team Product Owner has defined as highest priority Sprint Backlog – (SB) Chart showing how much work remaining in a Sprint Calculated in hours remaining Maintained by the Scrum Master daily Burndown Chart – (BC) Same as the Product Backlog. May involve one or more sprints dependent on determined Release date Release Backlog – (RB) Meetings Product backlog prepared prior to meeting First half – Team selects items committing to complete Additional discussion of PB occurs during actual Sprint Sprint Planning – Day 1 / First Half Team presents “done” code to PO and stakeholders Functionality not “done” is not shown Feedback generated - PB maybe reprioritized Scrum Master sets next Sprint Review Sprint Review Occurs after first half done – PO available for questions Team solely responsible for deciding how to build Tasks created / assigned – Sprint Backlog produced Sprint Planning – Day 1 / Second Half Held every day during a Sprint Lasts 15 minutes Team members report to each other not Scrum Master Asks 3 questions during meeting “What have you done since last daily scrum?” “What will you do before the next daily scrum?” “What obstacles are impeding your work?” Opportunity for team members to synchronize their work Daily Scrum Estimating “DONE”= Potentially Shippable! 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 Product Backlog - (PB) SCRUM CHEAT SHEET Attendees – SM and Team. PO is optional Questions – What went well and what can be improved? SM helps team in discovery – not provide answers Sprint Retrospective Roles Accountable for product success Defines all product features Responsible for prioritizing product features Maintains the Product Backlog Insures team working on highest valued features Product Owner (PO) 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 Scrum Master (SM) 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 Scrum Team FAQ Who decides when a Release happens? At the end of any given Sprint the PO can initiate a Release. Who is responsible for managing the teams? The teams are responsible for managing themselves. What is the length of a task? Tasks should take no longer than 16 hours. If longer then the task should be broken down further. Who manages obstacles? Primary responsibility is on the Scrum Master. However, teams must learn to resolve their own issues. If not able then escalated to SM. What are two of the biggest challenges in Scrum? Teams not self-managing, Scrum Master managing not leading. White Board containing teams 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 Task Board Tools Process Shippable Product Sprint Review Sprint Daily Scrum Sprint BacklogProduct Backlog Sprint Planning Sprint Retrospective 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: “As a <User> I want <function> So that <desired result> Story Example: As a user, I want to print a recipe so that I can cook it. User Stories 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 Example: “Send to a Friend” Story Points = 2 “Shopping Cart” Story Points = 9 Story Points Capacity = # Teammates (Productive Hrs x Sprint Days) Example – Team size is 4, Productive Hrs are 5, Sprint length is 30 days. Capacity = 4 (5 x30) = 600 hours NOTE: Account for vacation time during the Sprint! Estimate Team Capacity 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 Business Value Glossary of Terms Time Box - A period of time to finish a task. The end date is set and can not be changed Chickens – People that are not committed to the project and are not accountable for deliverables Pigs – People who are accountable for the project’s success Single Wringable Neck – This is the Product Owner! The rate at which team converts items to “DONE” in a single Sprint – Usually calculated in Story Points. Velocity Visibility + Flexibility = Scrum