You thought you understood Product Backlog

1,785 views

Published on

Ken Schwaber has given at the #14 agile vietnam monthly event a remote session about the product backlog in Scrum.

Published in: Education, Technology, Business
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,785
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
54
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

You thought you understood Product Backlog

  1. 1. Agile  Vietnam   May  28,  2012   Ken  Schwaber  Improving  the  Profession  of  So2ware  Development   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  2. 2. A  man  who  carries  a  cat  by  the  tail  learns  something  he   can  learn  in  no  other  way.   -­‐  Mark  Twain    Scrum  Professional  Scrum  Master     2   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  3. 3. 3  Types  of  Content  in  Scrum   Roles Artifacts Events • Product • Increment • Sprint Owner • Product • Sprint • Development Backlog Planning Team • Sprint • Daily Scrum • Scrum Master Backlog • Sprint Review • Retrospective 3   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  4. 4. Scrum  in  acIon   4   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  5. 5. What  Is  A  Requirement?   •  Something  required  in  soLware.   •  What,  not  how.   •  Not  implemenIng  a  database  or  a   infrastructure.   •  Describes  something  a  customer  can  directly   experience.   •  May  be  contained  in  a  Sprint,  Release,   Roadmap,  Goal,  Strategy.   5   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  6. 6. Product  Backlog   Product  Backlog  •  Inventory of things Cost:  13   to be done Cost:  20  •  Desirements Cost:  20   Cost:  3  •  Ordered based on Cost:  5  •  Transparent Cost:  1   Cost:  8  •  Minimal but Cost:  13   sufficient A   Cost:  3                         Cost:  100  •  Managed by Cost:  13   Product Owner 6   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  7. 7. Views  or  OrientaIon  into  Product  Backlog   System     Product  Backlog   •  Architecture   Business  System   Cost:  13   •  Layer   •  Work  flow   Cost:  20   •  Subsystem,   •  Process   Cost:  20   module,   •  AcIvity   Cost:  3   components   •  FuncIon   Cost:  5   Business  Process   Cost:  1   Persona   •  Workflow   Cost:  8   •  AcIvity   Cost:  13   •  Task   A   Cost:  3                         Cost:  100   New   Cost:  13   capability   7   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  8. 8. Major  League  Baseball  (MLB)  Vision   Vision   Strategies  Be  the  in  the  heart  of   •  Expand  worldwide  sports  fans  worldwide.   •  OpImize  revenues   •  Reach  down  and  up  in   age   •  Be  a  role  model   Vision   Strategy   TacIcs   Release   8   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  9. 9. MLB  Strategies   Strategy   TacIcs  •  OpImize  Revenues   •  Increase  adverIsing   revenues   •  Increase  adendance   •  Increase  number  of   leagues  and  teams   worldwide   •  Capture  more  of  “aLer   Vision   Strategy   TacIcs   Release   box  office  purchase”   revenues   9   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  10. 10. MLB  TacIcal  Roadmap   TacIc   Roadmap  •  Capture  more  of   •  Ensure  all  aLer  box   “aLer  box  office   office  revenues  are   legally  MLB’s   purchase”  revenues   •  Put  up  facility  for   trading  these  Ickets   •  Enforce  the  law   •  Increase  funcIonality   Vision   Strategy   TacIcs   Release   to  increase  revenue   capture   10   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  11. 11. Roadmap  Item  –  MLB  Tickets  (MLBTix)   MLBTix   The  Plan  •  Put  up  facility  for   •  Establish  fixed-­‐price   trading  these  Ickets   Icket  exchange  prior  •  Increase  funcIonality   to  opening  day   to  increase  revenue   •  Establish  aucIoning   capture   by  mid-­‐season   •  Establish  social  media   Vision   Strategy   TacIcs   Release   capabiliIes   11   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  12. 12. Requirements  oLen  have  three  components   Consumer   •   The  “consumer”  of  the  requirement   Requirement   •   What  the  user  will  consume   Acceptance   •  “…so  that…”  spells  out  boundaries  of   requirement  and  acceptance  tests  .  How   Criteria   to  know  if  a  requirement  is  saIsfied.   Developed  by  Development  Team   12   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  13. 13. Sprint    1  Forecast   13   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  14. 14. Sprint    2  Forecast   14   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  15. 15. Acceptance  Tests   15   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  16. 16. Acceptance  Tests   16   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  17. 17. PBI  Linked  to  System  and  Business  Processes   Capability  Packages,  Use   Common   Business    and   Scenarios  &  Stories  (Backlog   Architectural  Feature   Admin  Process   Items)   (Feature  Groups)   Hierarchies   (Feature  Groups)   BP1 CP1 CP2 CCA1 BP2 US1 CCA2 STORY1 CCA3BP3 STORY2 US3BP4 CCA4 STORY3 STORY4 STORY5 CCA5 BP5 US2 STORY6 CCA6BP6 STORY4 STORY7 CCA7BP7 STORY5 STORY6 CCA8 17   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  18. 18. Sprint  Planning  MeeIng  Flow   Dev.  Team   Product   Capacity   Backlog   Analyze, evaluate and select DefiniIon   Product Backlog for Sprint Standards,   Of  Done   ConvenIons   Guidelines   Establish Goal and forecast work Figure out how to do work; decompose it into actionable work plan Sprint  Backlog   18   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  19. 19. SelecIng  Product  Backlog   5  MINS   •  How  do  you  know  how  much  Product  Backlog   to  select  in  the  Sprint  Planning  meeIng?   •  If  the  definiIon  of  “done”  isn’t  in  place,  how   would  you  know  how  much  to  select?   •  What  is  the  value  of  knowing  the  definiIon  of   “done”  when  you  are  creaIng  the  product   backlog?     19   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  20. 20. Form  Sprint  Backlog   Product  Backlog   Sprint  Backlog   Sprint  Backlog   Cost:  13   Cost:  13   Cost:  0   Cost:  20   Cost:  20   Cost:  2   Cost:  20   Cost:  20   Cost3   Cost:  3   Cost:  5   Cost:  5   Cost:  3   Cost:  1   Cost:  8   Cost:  0   Cost:  13   Cost:10   A   Cost:  3                         Cost10   Cost:  100   Cost:  13   Cost:  20   20   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  21. 21. Test  First  Development  Kanban  Training  Wheels   Lane   1   2   3   4   5   What  1   Develop   Detailed   Automate  all   Test   Fix  and   Acceptance   Design   tests   soLware   repeat  4   tests  for   and  doc.   unIl  all   PBIs   works   Who  1   Whole  team   Whole   QA,  Analyst   Whole  team   Whole  team   team   What  2   Write  unit  tests   and  code   Who  2   Designers,   programmers   What  3   Write   documentaIon   Who  3   Tech  writers   21   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  22. 22. Sample  Sprint  Backlog  Board   22   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  23. 23. Backlog  Grooming  •  Grooming  means   –  Planning  the  PBL  to  an  acIonable  level  of  detail   –  Maintaining  a  Rolling  Backlog  ProjecIon  •  Plan  10%  of  each  Sprint  to  be  spent     grooming  the  Product  Backlog  •  Top  ordered  Product  Backlog  items  are  well  understood   and  easily  selected  in  Sprint  Planning  •  Never  allow  the  Product  Owner  to  go  into  the  Sprint   Planning  meeIng  with  an  un-­‐groomed  Product  Backlog.   23   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  24. 24. Sprint  Review   Restore  unfinished  product   backlog  to  PB   Reformulate  development  team   Increment   Rearrange  PB  for  new   opportuniIes   Sprint   Sprint   Release  one  or  more   Analysis   Review   increments  of  funcIonality   Stop  SprinIng   Product   Add  more  Scrum  Teams   Backlog   CollaboraAve  working  session  of  Scrum   Team  and  key  stakeholders   24   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  25. 25. Sprint  RetrospecIves   •  Scrum Team inspects how the last Sprint went Sprint  Review   •  Scrum Team selects several improvements •  Scrum Team implements improvements for next Sprint(s) Sprint   Time  line  of  Events  in  Sprint   25   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  26. 26. Sprint  RetrospecIve  Books   26   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  27. 27. SoLware  in  30  Days   Wiley,  April 2012 Ken Schwaber & Jeff Sutherland “We  hold  these  truths  to  be   self-­‐evident,  that  all  men   are  created  equal,  that  they   are  endowed  by  their   Creator  with  certain   unalienable  Rights,  that   among  these  Life,  Liberty   and  the  pursuit  of   Happiness  and  SoLware  in   30  Days.” 27   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  28. 28. Next  Steps   Stay  Connected   Subscribe  to  our  RSS  feed  to  receive  the  latest  updates  on  Scrum.org  programs,   training,  and  cerIficaIons.  hdp://www.scrum.org/news/rss.xml   Follow  us  on  Twider  at  @scrumdotorg   Engage   Join  the  Yahoo!  discussion  group  where  you  can  tap  into  the  collecIve   knowledge  of  Scrum  users  around  the  world.   hdp://groups.yahoo.com/group/scrumdevelopment/     If  you  achieve  PSM  cerIficaIon  you  are  eligible  to  join  the  LinkedIn  group  to   conInue  the  conversaIons  with  the  people  you’ve  met  in  this  class,  and  start   new  ones  with  other  PSMs.   28   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  
  29. 29. Thank     You!   29   ©  1993-­‐2011  Scrum.org,  All  Rights  Reserved  

×