Recommended
More Related Content
Viewers also liked
Similar to Better Quality through Scrum (2011)
Similar to Better Quality through Scrum (2011) (20)
More from Dominik Jungowski
More from Dominik Jungowski (18)
Recently uploaded
Recently uploaded (20)
Better Quality through Scrum (2011)
- 1. Dominik Jungowski | CHIP Xonio Online GmbH Better Quality through Scrum
- 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. Agenda What is Scrum? How Scrum works MeeDngs, ArDfacts & Roles DefiniDon of Done Bugs DeducDons Scrum at CHIP
- 5. Scrum is... like a recipe
- 7. A classical team Stakeholder Developer Stakeholder Developer Project manager Customer Developer Customer Developer
- 8. A Scrum team Stakeholder ScrumMaster Stakeholder Developer Product Owner Team Customer Developer Customer Developer
- 10. How Scrum works Agile project management IteraDons („sprints“) Framework Inspect & Adapt
- 11. How Scrum works Sprint Product Product Project Sprint Product Backlog Sprint Product Potentially shippable product after each sprint
- 12. How Scrum works EsDmated Sprint Planning I Sprint Planning II Product Backlog Sprint Backlog regularly The Scrum Process every day EsDmaDon MeeDng Daily Standup RetrospecDve Review MeeDng MeeDng Product Backlog
- 14. Product Backlog Meetings & Artifacts Maintained by the Product Owner Consists of user stories PrioriDzed EsDmated in EsDmaDon MeeDng
- 15. Estimation Meeting What‘s about to come?
- 16. EsDmaDon MeeDng Meetings & Artifacts User stories esDmated in storypoints EsDmated by whole team Knowing what will come Regularly
- 17. EsDmaDon MeeDng Meetings & Artifacts
- 18. Sprint Planning I Setting the goal
- 19. Sprint Planning I Meetings & Artifacts Product Owner presents the Sprintgoal Product Owner presents the user stories Team pulls the user stories Acceptance criteria, etc. are wriZen down
- 20. Sprint Planning II How to reach the goal
- 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. Sprint Planning II Meetings & 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. Daily Standup Where do we stand?
- 24. Daily Standup Meetings & 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. Daily Standup Meetings & Artifacts What have I done since the last standup? What will I do unDl the next standup? What‘s impeding me?
- 27. Sprint Backlog Meetings & Artifacts Work in User Story To Do Done Progress Story 1 Task Task Task Story 2 Task Story 3 Task Task
- 28. Sprint Backlog Meetings & Artifacts
- 29. Sprint Backlog Meetings & Artifacts
- 30. Burndown Chart Meetings & Artifacts $)# !"# !*# !$# !)# %&# %&# %&# %*# %'# %)# '*# ')# ')# (# *# )# )# )# %(+),# !)+),# )$+')# )&+')# )(+')#
- 31. Review Meeting Let‘s show the cake!
- 32. 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
- 33. Review MeeDng Meetings & Artifacts Only completed, working so_ware is presented No slides!
- 34. Review MeeDng The cake is not a lie!
- 35. Retrospective Meeting Improving the cake
- 37. RetrospecDve MeeDng Meetings & 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
- 38. Inspect & Adapt
- 40. Tweaking your improvements Rat - Maze - Experiment Experiment by Tolman & Honzik in 1930 3 groups / 17 days
- 41. Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' #!" +" *" )" (" !"#$%&#'($$)$*' '" ,-./0"%" &" %" $" #" !" #" $" %" &" '" (" )" *" +" #!" ##" #$" #%" #&" #'" #(" #)" +%,*'
- 42. Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' '#" '!" &" !"#$%&#'($$)$*' %" ,-./0"#" ,-./0"(" $" #" !" '" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*" +%,*'
- 43. Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' '#" '!" &" !"#$%&#'($$)$*' %" ,-./0"'" ,-./0"#" ,-./0"(" $" #" !" '" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*" +%,*'
- 45. Have a BBQ!
- 46. Roles
- 47. Product Owner Responsible for the product Maintains the Product Backlog Has the vision
- 49. ScrumMaster Monitors the Scrum process Causes course correcDon Removes impediments Protects the team
- 50. Impediments Disturb the team Hold back the team Impediment Backlog (like Sprint Backlog)
- 53. Definition of Done Work in User Story To Do Done Progress TaskStory 1Task Tas TaskStory 2 TaskStory 3 Task
- 54. Definition of Done Checklist Defines when Tasks can be moved to „Done“ Defines when User Stories can be moved to „Done“
- 55. Definition of Done Responsibility lies with the team Maintained by the team only PotenDally shippable product every day
- 56. Definition of Done Example: DoD for Tasks Unit Tested Runs in the following browsers: Firefox, Internet Explorer, Chrome, Safari No broken unit tests Refactored Reviewed
- 57. Definition of Done Example: DoD for User Stories No broken unit tests Merged into trunk AddiDonal criteria for specific user stories can be set in Sprint Planning I
- 58. Bugs
- 59. Bugs Put them on your Sprint Backlog Fix them immediately! Fixed at best unDl the next daily standup If possible: Don‘t use bugtrackers
- 60. Bugs Work in User Story To Do Done Progress TaskStory 1Task Tas Story 2 Task Bug Story 3 Task Task
- 61. Sprint Backlog Meetings & Artifacts
- 62. Bugs $)" $+" $+" $!" $!" $#" $$" $$" $&" $&" (" (" (" )" )" %" %" +" *" !" !" !" '" '" '" #" #" #" #" #" $" &" '&" '$" '#" ''" '!" '*" '+" '%" ')" '(" !&" !$" !#" !'" !!" !*" !"#$%&'
- 63. Bugs 100 90,64 90 82,33 80 70 66,95 60 57,39 52,32 48,07 50 44,23 Stunden 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 !"#$%&'
- 64. Bugs !"#$%&%'()*+,)-.(% 00.001 00.001 00.000 00.000 00.000 00.000 00.000 2 5 8 11 15 18 21 24 27 30
- 65. Bugs Example: DoD for Bugs Unit tested No broken unit tests Fixed in the following browsers: Firefox, Internet Explorer, Chrome, Safari Distributed to all web servers
- 66. Bugs What about old Bugtracker lists? Fix all the bugs or Delete the list
- 67. Deductions
- 68. Deductions No upfront design constant refactoring
- 69. Deductions Working at the same Pair Programming user story
- 70. Deductions Code Reviews Pair Programming
- 71. Deductions Collective Code Team commitment Ownership
- 72. Deductions Collective Code Pair Programming Ownership
- 73. Deductions Fixing bugs immediately Test - Driven Nobody likes fixing bugs Development Definition of Done
- 74. Deductions Test - Driven Continuous Development Integration
- 75. Scrum at CHIP (Price comparison only)
- 76. Bugs per Month *)#))& !"#$%& !$#))& !)#))& !))%& '$#))& !))(& '$#))& '!#(!& ''#))& !)')& ')#))& !)''& $#))& )#))&
- 77. Items per Person %*$ %&$ %)$ %($ '$ *$ &$ )$ !"#$ %&"'$ ($ +,-./$('$0$+12134$('$ +,-./$(5$0$+12134$(5$
- 78. „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/
- 79. Questions?
- 80. Literature Ken Schwaber: „Agile Project Management with Scrum“ (Microsoft Press)
- 81. Literature Boris Gloger: „Scrum: Produkte zuverlässig und schnell entwickeln“ (Hanser Fachbuch)
- 82. Literature Mike Cohn: „Succeeding with Agile: Software Development using Scrum“ (Addison-Wesley Signature)
- 83. We‘re hiring! Developer for price comparison and more - see www.chipxonio.de
- 84. Thank you! Twitter: @djungowski Blog: www.phpdevblog.net