Dominik Jungowski | CHIP Xonio Online GmbHBetter Quality through Scrum
About me 26	  years	  old Working	  at	  CHIP	  Xonio	  Online	  GmbH Developer	  and	  ScrumMaster	  for	  price	  compar...
Agenda What	  is	  Scrum? How	  Scrum	  works MeeDngs,	  ArDfacts	  &	  Roles DefiniDon	  of	  Done Bugs DeducDons Scrum	  ...
What is Scrum?
Scrum is...              like	  a	  recipe
Scrum is not...
A classical teamStakeholder                        DeveloperStakeholder                        Developer              Proj...
A Scrum teamStakeholder                      ScrumMasterStakeholder                       Developer              Product	 ...
How Scrum works
How Scrum works Agile	  project	  management IteraDons	  („sprints“) Framework Inspect	  &	  Adapt
How Scrum works                                Sprint        Product                Product	   Project                    ...
How Scrum works   EsDmated	                            Sprint	  Planning	  I   Sprint	  Planning	  IIProduct	  Backlog    ...
Meetings & Artifacts
Product	  BacklogMeetings & Artifacts Maintained	  by	  the	  Product	  Owner Consists	  of	  user	  stories PrioriDzed Es...
Estimation Meeting What‘s about to come?
EsDmaDon                                                     MeeDngMeetings & Artifacts User	  stories	  esDmated	  in	  s...
EsDmaDon                        MeeDngMeetings & Artifacts
Sprint Planning I     Setting the goal
Sprint	  Planning	  IMeetings & Artifacts Product	  Owner	  presents	  the	  Sprintgoal Product	  Owner	  presents	  the	 ...
Sprint Planning II      How to reach the goal
Sprint	  Planning	  II  Meetings & Artifacts„The	  result	  of	  this	  mee/ng	  is,	  that	  everybody	  knows	  how	  th...
Sprint	  Planning	  IIMeetings & Artifacts Tasks	  for	  selected	  user	  stories	  are	  generated Generated	  tasks	  t...
Daily Standup   Where do we stand?
Daily	  StandupMeetings & Artifacts Same	  Dme,	  same	  place,	  every	  day! Team	  sychronizes	  itself Sprint	  Backlo...
Daily	  StandupMeetings & Artifacts What	  have	  I	  done	  since	  the	  last	  standup? What	  will	  I	  do	  unDl	  t...
Sprint	  Backlog  Meetings & Artifacts                                Work inUser Story        To Do                      ...
Sprint	  BacklogMeetings & Artifacts
Sprint	  BacklogMeetings & Artifacts
Burndown	  Chart      Meetings & Artifacts$)#        !"#!*#            !$#!)#                       %&#    %&#     %&#%*# ...
Review Meeting    Let‘s show the cake!
Review	  MeeDng  Meetings & Artifacts„The	  Scrum-­‐Team	  shows	  the	  results	  of	  their	  work	  to	  the	  End	  Us...
Review	  MeeDngMeetings & Artifacts Only	  completed,	  working	  so_ware	  is	  presented No	  slides!
Review	  MeeDngThe cake is not a lie!
Retrospective Meeting        Improving the cake
RetrospecDve	                                                                 MeeDngMeetings & Artifacts Team	  reflects	  ...
Inspect & Adapt
Tweaking yourimprovements
Tweaking your improvements     Rat - Maze - Experiment       Experiment by Tolman & Honzik in 1930                3 groups...
Tweaking your improvements                                                        -%.*/0%1#/(23#$45#6.                   #...
Tweaking your improvements                                                        -%.*/0%1#/(23#$45#6.                   #...
Tweaking your improvements                                                        -%.*/0%1#/(23#$45#6.                   #...
Reward your team!
Have a BBQ!
Roles
Product Owner Responsible	  for	  the	  product Maintains	  the	  Product	  Backlog Has	  the	  vision
TeamSelf	  -­‐	  organizedDeliversDeliversDelivers
ScrumMaster Monitors	  the	  Scrum	  process Causes	  course	  correcDon Removes	  impediments Protects	  the	  team
Impediments Disturb	  the	  team Hold	  back	  the	  team Impediment	  Backlog	  (like	  Sprint	  Backlog)
Definition of Done
Definition of Done                     Work inUser Story   To Do                   Done                     Progress      ...
Definition of Done Checklist Defines	  when	  Tasks	  can	  be	  moved	  to	  „Done“ Defines	  when	  User	  Stories	  can	 ...
Definition of Done Responsibility	  lies	  with	  the	  team Maintained	  by	  the	  team	  only PotenDally	  shippable	  ...
Definition of DoneExample:	  DoD	  for	  Tasks    Unit	  Tested    Runs	  in	  the	  following	  browsers:	  Firefox,	  In...
Definition of DoneExample:	  DoD	  for	  User	  Stories    No	  broken	  unit	  tests    Merged	  into	  trunk   AddiDonal...
Bugs
Bugs Put	  them	  on	  your	  Sprint	  Backlog Fix	  them	  immediately! Fixed	  at	  best	  unDl	  the	  next	  daily	  s...
Bugs                           Work inUser Story       To Do                      Done                           Progress ...
Sprint	  BacklogMeetings & Artifacts
Bugs$)"$+"                                                      $+"$!"                                                    ...
Bugs          100                                                              90,64           90                         ...
Bugs                     !"#$%&%()*+,)-.(%00.00100.00100.00000.00000.00000.00000.000         2   5   8   11        15     ...
BugsExample:	  DoD	  for	  Bugs    Unit	  tested    No	  broken	  unit	  tests    Fixed	  in	  the	  following	  browsers:...
BugsWhat	  about	  old	  Bugtracker	  lists?    Fix	  all	  the	  bugs	  or    Delete	  the	  list
Deductions
DeductionsNo upfront design   constant refactoring
DeductionsWorking at the same                      Pair Programming     user story
Deductions  Code Reviews   Pair Programming
Deductions                  Collective CodeTeam commitment                    Ownership
Deductions                   Collective CodePair Programming                     Ownership
DeductionsFixing bugs immediately                           Test - DrivenNobody likes fixing bugs                         ...
Deductions Test - Driven   Continuous Development     Integration
Scrum at CHIP  (Price comparison only)
Bugs per Month*)#))&         !"#$%&!$#))&!)#))&                                       !))%&                           $#))...
Items per Person%*$%&$%)$%($ $ *$ &$ )$              !"#$                   %&"$ ($      +,-./$($0$+12134$($   +,-./$(5$0$...
„Companies,	  managers	  should	  understand,	  that	  their	  employees	  want	  to	  work.	  Trust	  them,	  that	  they...
Questions?
Literature             Ken Schwaber: „Agile Project             Management with Scrum“             (Microsoft Press)
Literature             Boris Gloger: „Scrum: Produkte             zuverlässig und schnell             entwickeln“         ...
Literature             Mike Cohn: „Succeeding with             Agile: Software Development             using Scrum“       ...
We‘re hiring! Developer for price comparisonand more - see www.chipxonio.de
Thank you!   Twitter: @djungowskiBlog: www.phpdevblog.net
Better Quality through Scrum (2011)
Better Quality through Scrum (2011)
Better Quality through Scrum (2011)
Upcoming SlideShare
Loading in...5
×

Better Quality through Scrum (2011)

609

Published on

2011 Edition of my Better Quality through Scrum session

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

No Downloads
Views
Total Views
609
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
26
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Better Quality through Scrum (2011)

  1. 1. Dominik Jungowski | CHIP Xonio Online GmbHBetter Quality through Scrum
  2. 2. About me 26  years  old Working  at  CHIP  Xonio  Online  GmbH Developer  and  ScrumMaster  for  price  comparison Part  -­‐  Dme  studies  in  psychology  at  FernUni  Hagen
  3. 3. Agenda What  is  Scrum? How  Scrum  works MeeDngs,  ArDfacts  &  Roles DefiniDon  of  Done Bugs DeducDons Scrum  at  CHIP
  4. 4. What is Scrum?
  5. 5. Scrum is... like  a  recipe
  6. 6. Scrum is not...
  7. 7. A classical teamStakeholder DeveloperStakeholder Developer Project  manager Customer Developer Customer Developer
  8. 8. A Scrum teamStakeholder ScrumMasterStakeholder Developer Product  Owner Team Customer Developer Customer Developer
  9. 9. How Scrum works
  10. 10. How Scrum works Agile  project  management IteraDons  („sprints“) Framework Inspect  &  Adapt
  11. 11. How Scrum works Sprint Product Product   Project Sprint Product Backlog Sprint ProductPotentially shippable product after each sprint
  12. 12. How Scrum works EsDmated   Sprint  Planning  I Sprint  Planning  IIProduct  Backlog Sprint  Backlog regularly The Scrum Process every day EsDmaDon MeeDng Daily  Standup RetrospecDve   Review  MeeDng MeeDngProduct  Backlog
  13. 13. Meetings & Artifacts
  14. 14. Product  BacklogMeetings & Artifacts Maintained  by  the  Product  Owner Consists  of  user  stories PrioriDzed EsDmated  in  EsDmaDon  MeeDng
  15. 15. Estimation Meeting What‘s about to come?
  16. 16. EsDmaDon MeeDngMeetings & Artifacts User  stories  esDmated  in  storypoints EsDmated  by  whole  team Knowing  what  will  come Regularly
  17. 17. EsDmaDon MeeDngMeetings & Artifacts
  18. 18. Sprint Planning I Setting the goal
  19. 19. Sprint  Planning  IMeetings & Artifacts Product  Owner  presents  the  Sprintgoal Product  Owner  presents  the  user  stories Team  pulls  the  user  stories Acceptance  criteria,  etc.  are  wriZen  down
  20. 20. Sprint Planning II How to reach the goal
  21. 21. Sprint  Planning  II Meetings & Artifacts„The  result  of  this  mee/ng  is,  that  everybody  knows  how  the  team  can  cope  the  tasks  together.  You  do  not  decide  on  who  does  what.“ -­‐  Boris  Gloger,  Scrum:  Produkte  zuverlässig  und  schnell  entwickeln
  22. 22. Sprint  Planning  IIMeetings & Artifacts Tasks  for  selected  user  stories  are  generated Generated  tasks  take  no  longer  than  8  hours  /  1   workday Sprint  Backlog  is  created Everybody  knows  about  the  „how“
  23. 23. Daily Standup Where do we stand?
  24. 24. Daily  StandupMeetings & Artifacts Same  Dme,  same  place,  every  day! Team  sychronizes  itself Sprint  Backlog  is  updated Burndown  Chart  is  updated Public Time  for  discussion  a_erwards
  25. 25. Daily  StandupMeetings & Artifacts What  have  I  done  since  the  last  standup? What  will  I  do  unDl  the  next  standup? What‘s  impeding  me?
  26. 26. Sprint  Backlog Meetings & Artifacts Work inUser Story To Do Done Progress Story  1 Task Task Task Story  2 Task Story  3 Task Task
  27. 27. Sprint  BacklogMeetings & Artifacts
  28. 28. Sprint  BacklogMeetings & Artifacts
  29. 29. Burndown  Chart Meetings & Artifacts$)# !"#!*# !$#!)# %&# %&# %&#%*# %#%)#*# )#)# (# *# )# )# )# %(+),# !)+),# )$+)# )&+)# )(+)#
  30. 30. Review Meeting Let‘s show the cake!
  31. 31. Review  MeeDng Meetings & Artifacts„The  Scrum-­‐Team  shows  the  results  of  their  work  to  the  End  User.  The  team  members  want  to  have  feedback.  This  feedback  can  be  used  to  create  or  change  Backlog  Items.“ -­‐  Scrum  with  Boris  Gloger
  32. 32. Review  MeeDngMeetings & Artifacts Only  completed,  working  so_ware  is  presented No  slides!
  33. 33. Review  MeeDngThe cake is not a lie!
  34. 34. Retrospective Meeting Improving the cake
  35. 35. RetrospecDve   MeeDngMeetings & Artifacts Team  reflects  on  last  sprint „Learning  from  the  past  for  the  future“ Output: Things  the  Team  wants  to  improve Impediments Similar  to  a  debriefing
  36. 36. Inspect & Adapt
  37. 37. Tweaking yourimprovements
  38. 38. Tweaking your improvements Rat - Maze - Experiment Experiment by Tolman & Honzik in 1930 3 groups / 17 days
  39. 39. Tweaking your improvements -%.*/0%1#/(23#$45#6. #!" +" *" )" (" !"#$%&#($$)$* " ,-./0"%" &" %" $" #" !" #" $" %" &" " (" )" *" +" #!" ##" #$" #%" #&" #" #(" #)" +%,*
  40. 40. Tweaking your improvements -%.*/0%1#/(23#$45#6. #" !" &" !"#$%&#($$)$* %" ,-./0"#" ,-./0"(" $" #" !" " #" (" $" )" %" *" &" +" !" " #" (" $" )" %" *" +%,*
  41. 41. Tweaking your improvements -%.*/0%1#/(23#$45#6. #" !" &" !"#$%&#($$)$* %" ,-./0"" ,-./0"#" ,-./0"(" $" #" !" " #" (" $" )" %" *" &" +" !" " #" (" $" )" %" *" +%,*
  42. 42. Reward your team!
  43. 43. Have a BBQ!
  44. 44. Roles
  45. 45. Product Owner Responsible  for  the  product Maintains  the  Product  Backlog Has  the  vision
  46. 46. TeamSelf  -­‐  organizedDeliversDeliversDelivers
  47. 47. ScrumMaster Monitors  the  Scrum  process Causes  course  correcDon Removes  impediments Protects  the  team
  48. 48. Impediments Disturb  the  team Hold  back  the  team Impediment  Backlog  (like  Sprint  Backlog)
  49. 49. Definition of Done
  50. 50. Definition of Done Work inUser Story To Do Done Progress TaskStory  1Task Tas TaskStory  2 TaskStory  3 Task
  51. 51. Definition of Done Checklist Defines  when  Tasks  can  be  moved  to  „Done“ Defines  when  User  Stories  can  be  moved  to   „Done“
  52. 52. Definition of Done Responsibility  lies  with  the  team Maintained  by  the  team  only PotenDally  shippable  product  every  day
  53. 53. Definition of DoneExample:  DoD  for  Tasks Unit  Tested Runs  in  the  following  browsers:  Firefox,  Internet  Explorer,   Chrome,  Safari No  broken  unit  tests Refactored Reviewed
  54. 54. Definition of DoneExample:  DoD  for  User  Stories No  broken  unit  tests Merged  into  trunk AddiDonal  criteria  for  specific  user  stories  can  be   set  in  Sprint  Planning  I
  55. 55. Bugs
  56. 56. Bugs Put  them  on  your  Sprint  Backlog Fix  them  immediately! Fixed  at  best  unDl  the  next  daily  standup If  possible:  Don‘t  use  bugtrackers
  57. 57. Bugs Work inUser Story To Do Done Progress TaskStory  1Task Tas Story  2 Task Bug Story  3 Task Task
  58. 58. Sprint  BacklogMeetings & Artifacts
  59. 59. Bugs$)"$+" $+"$!" $!"$#" $$" $$"$&" $&" (" (" (" )" )" %" %" +" *" !" !" !" " " " #" #" #" #" #" $" &" &" $" #" " !" *" +" %" )" (" !&" !$" !#" !" !!" !*" !"#$%&
  60. 60. Bugs 100 90,64 90 82,33 80 70 66,95 60 57,39 52,32 48,07 50 44,23Stunden 40 33,22 29,26 30 19,87 17,03 20 15,27 6,56 7,87 7,23 10 0,67 0 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 !"#$%&
  61. 61. Bugs !"#$%&%()*+,)-.(%00.00100.00100.00000.00000.00000.00000.000 2 5 8 11 15 18 21 24 27 30
  62. 62. BugsExample:  DoD  for  Bugs Unit  tested No  broken  unit  tests Fixed  in  the  following  browsers:  Firefox,  Internet  Explorer,   Chrome,  Safari Distributed  to  all  web  servers
  63. 63. BugsWhat  about  old  Bugtracker  lists? Fix  all  the  bugs  or Delete  the  list
  64. 64. Deductions
  65. 65. DeductionsNo upfront design constant refactoring
  66. 66. DeductionsWorking at the same Pair Programming user story
  67. 67. Deductions Code Reviews Pair Programming
  68. 68. Deductions Collective CodeTeam commitment Ownership
  69. 69. Deductions Collective CodePair Programming Ownership
  70. 70. DeductionsFixing bugs immediately Test - DrivenNobody likes fixing bugs DevelopmentDefinition of Done
  71. 71. Deductions Test - Driven Continuous Development Integration
  72. 72. Scrum at CHIP (Price comparison only)
  73. 73. Bugs per Month*)#))& !"#$%&!$#))&!)#))& !))%& $#))& !))(&$#))& !#(!& #))& !))&)#))& !)& $#))& )#))&
  74. 74. Items per Person%*$%&$%)$%($ $ *$ &$ )$ !"#$ %&"$ ($ +,-./$($0$+12134$($ +,-./$(5$0$+12134$(5$
  75. 75. „Companies,  managers  should  understand,  that  their  employees  want  to  work.  Trust  them,  that  they  want  to  do  a  good  job.“hLp://feedproxy.google.com/~r/borisgloger-­‐de/~3/U2zztp7jcW8/
  76. 76. Questions?
  77. 77. Literature Ken Schwaber: „Agile Project Management with Scrum“ (Microsoft Press)
  78. 78. Literature Boris Gloger: „Scrum: Produkte zuverlässig und schnell entwickeln“ (Hanser Fachbuch)
  79. 79. Literature Mike Cohn: „Succeeding with Agile: Software Development using Scrum“ (Addison-Wesley Signature)
  80. 80. We‘re hiring! Developer for price comparisonand more - see www.chipxonio.de
  81. 81. Thank you! Twitter: @djungowskiBlog: www.phpdevblog.net
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×