Upload
krishna-sankar
View
1.471
Download
3
Embed Size (px)
DESCRIPTION
Scrum debrief to team after my training & ScrumMaster certification.
Citation preview
Scrum debrief
5/16/12
Krishna Sankar
What is scrum ?
• Scrum is an itera:ve & incremental agile process for soAware development
• It doesn’t change the physics but can make the team more efficient & working more streamlined
• It also increases the visibility of the work done & backlog to all
• Has emerged as the most common methodology for soAware development
What is scrum ?
• Instead of ad-‐hoc development a product is broken into small pieces called user stories and developed in sprints
• 1986 HBR ar:cle – Studied new product dev from Xerox, Canon, Honda, 3M, …
– From a “relay-‐race” method to a “rugby” approach
Scrum Framework (In one slide)
• Decompose a product into features & smaller ver:cal slices called User Stories
• The team works on a set of user stories in a :me boxed (2 week) basic development unit called a sprint/itera:on
• AAer each sprint, work is reviewed and progress is accessed
• And next sprint starts …. • Un:l all the features in the backlog are developed
Why Scrum
• Efficient feature velocity – Develop ver:cal slices of value
• Con:nuous engagement between business & development
• Smaller cycles of development – 1 to 4 weeks, Typically 2 weeks
• Engaged team, progress visible to all • But requires discipline & commitment
Scrum
• Small cohesive teams – 7 ± 2 members
• Easily stay together for 2-‐3 years – Very similar to a jazz quartet
Release Planning
User Stories
• 3 Roles – Team, Product Owner, Scrum Master
• 3 meetings – Scrum Planning, Daily Scrum,
Retrospec:ve • 3 Artifacts
– Product Backlog, Sprint Backlog, Burndown Chart
• Framework – Collec:on of prac:ces & concepts
around which a process can be built
Release Planning
User Stories
• Product Owner – Owns the features – Priori:zes the features – Decomposes into user stories
– Cer:fies “work done”
Release Planning
User Stories
• Team – Develops & delivers user stories – Works with Product Owner to decompose features to user stories & tasks
– Helps es:ma:on • Scrum Master
– Facilitator
Release Planning
User Stories
1
2
4
5
6
8 3
7
#1 : Release Planning – Compose product into features
– Features go into a backlog – Once backlog is completed, the release is done
Release Planning
User Stories
1
2
4
5
6
8 3
7#2 : Decompose Features into User Stories
– User Story is a ver:cal slice that can be delivered in 2 weeks • As <user> • I want <ac:on> • so that <value>
– Es:mate rela:ve size
Release Planning
User Stories
1
2
4
5
6
8 3
7
#3 : Sprint Planning – Start of every sprint – 2 hrs (Tuesday AM) – Commit To user stories – Decompose into tasks
Release Planning
User Stories
1
2
4
5
6
8 3
7
#4 : 2-Week Sprint (Timeboxed) – Do work – Ask ques:ons to Prod Owner
– Dev & Test built-‐in – Con:nuous Integra:on
Release Planning
User Stories
1
2
4
5
6
8 3
7
#5 : Daily Standup Meeting – Coordina:on mee:ng – What is impeding your work ?
– What did you yesterday ? – What will you do today ?
Release Planning
User Stories
1
2
4
5
6
8 3
7
#6 : Sprint Review – At the end of every sprint – Demo of developed feature
– PO says “Done” or “Not Done”
Release Planning
User Stories
1
2
4
5
6
8 3
7
#7 : Sprint Retrospect – AAer each sprint – Lessons Learned – What can be improved
Release Planning
User Stories
1
2
4
5
6
8 3
7
#8 : PO adjusts Backlog, Team starts next sprint – Based on current priori:es
Burn Chart
• Shown work done vs. Time • Visibility into project • Es:ma:on • Feedback
References 1. hmp://www.cprime.com/community/ar:cles/whentousescrum.html 2. Lecture Notes & CSM class by Mark Levison 3. hmp://pm:ps.net/adap:ng-‐agile-‐methodology-‐startup/ 4. www.rallydev.com 5. hmp://blog.crisp.se/2011/12/07/anderslaestadius/improving-‐the-‐daily-‐
scrum 6. hmp://www.sao.corvallis.or.us/drupal/files/The%20New%20New
%20Product%20Development%20Game.pdf 7. Essen:al Scrum: A Prac:cal Guide to the Most Popular Agile Process -‐
hmp://www.amazon.com/Essen:al-‐Scrum-‐Prac:cal-‐Addison-‐Wesley-‐Signature/dp/0137043295/