Your SlideShare is downloading. ×
0
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Scrum debrief to team
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Scrum debrief to team

1,053

Published on

Scrum debrief to team after my training & ScrumMaster certification.

Scrum debrief to team after my training & ScrumMaster certification.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,053
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
12
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Scrum  debrief   5/16/12   Krishna  Sankar  
  • 2. 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    
  • 3. 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  
  • 4. 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  
  • 5. 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  
  • 6. Scrum  •  Small  cohesive  teams   –  7  ±  2  members  •  Easily  stay  together  for  2-­‐3  years   –  Very  similar  to  a  jazz  quartet  
  • 7. Release  Planning   •  3 Roles –  Team,  Product  Owner,  Scrum  Master   •  3 meetings –  Scrum  Planning,  Daily  Scrum,   Retrospec:ve   •  3 Artifacts User   –  Product  Backlog,  Sprint  Backlog,   Stories   Burndown  Chart   •  Framework –  Collec:on  of  prac:ces  &  concepts   around  which  a  process  can  be  built    
  • 8. Release  Planning   •  Product Owner –  Owns  the  features   –  Priori:zes  the  features   User   Stories   –  Decomposes  into  user   stories   –  Cer:fies  “work  done”  
  • 9. Release  Planning   •  Team –  Develops  &  delivers  user  stories   –  Works  with  Product  Owner  to   decompose  features  to  user   stories  &  tasks   User   Stories   –  Helps  es:ma:on   •  Scrum Master –  Facilitator  
  • 10. 5Release  Planning   8 3 4 6 1 7 #1 : Release Planning –  Compose  product  into   features   User   –  Features  go  into  a  backlog   2 Stories   –  Once  backlog  is  completed,   the  release  is  done  
  • 11. 5Release  Planning   8 3 4 6 1 7 #2 : Decompose Features into User Stories –  User  Story  is  a  ver:cal  slice  that   can  be  delivered  in  2  weeks     •  As  <user>   User   •  I  want  <ac:on>   2 Stories   •  so  that  <value>     –  Es:mate  rela:ve  size  
  • 12. 5Release  Planning   8 3 4 6 1 7 #3 : Sprint Planning –  Start  of  every  sprint   –  2  hrs  (Tuesday  AM)     User   2 Stories   –  Commit  To  user  stories   –  Decompose  into  tasks  
  • 13. 5Release  Planning   8 3 4 6 1 7 #4 : 2-Week Sprint (Timeboxed) –  Do  work   –  Ask  ques:ons  to  Prod   User   2 Stories   Owner   –  Dev  &  Test  built-­‐in   –  Con:nuous  Integra:on  
  • 14. 5Release  Planning   8 3 4 6 1 7 #5 : Daily Standup Meeting –  Coordina:on  mee:ng   –  What is impeding your User   work ? 2 Stories   –  What did you yesterday ? –  What will you do today ?
  • 15. 5Release  Planning   8 3 4 6 1 7 #6 : Sprint Review –  At  the  end  of  every  sprint   –  Demo  of  developed   User   feature   2 Stories   –  PO  says  “Done”  or  “Not   Done”  
  • 16. 5Release  Planning   8 3 4 6 1 7 #7 : Sprint Retrospect –  AAer  each  sprint   –  Lessons  Learned   User   2 Stories   –  What  can  be  improved  
  • 17. 5Release  Planning   8 3 4 6 1 7 #8 : PO adjusts Backlog, Team starts next sprint –  Based  on  current   User   2 Stories   priori:es  
  • 18. Burn  Chart  •  Shown  work  done  vs.  Time  •  Visibility  into  project  •  Es:ma:on  •  Feedback    
  • 19. 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/  

×