Better Quality through Scrum
- 1. Dominik Jungowski | CHIP Xonio Online GmbH Better Quality through Scrum Montag, 11. Oktober 2010
- 2. About me • 26 years old • Working at CHIP Xonio Online GmbH • Developer and ScrumMaster for price comparison • Part - time studies in psychology at FernUni Hagen Montag, 11. Oktober 2010
- 3. Agenda • What is Scrum? • How Scrum works • Meetings, Artifacts & Roles • Definition of Done • Bugs • Deductions • Scrum at CHIP Montag, 11. Oktober 2010
- 4. What is Scrum? Montag, 11. Oktober 2010
- 5. Scrum is... like a recipe Montag, 11. Oktober 2010
- 6. Scrum is not... Montag, 11. Oktober 2010
- 7. A classical team Stakeholder Developer Stakeholder Developer Project manager Customer Developer Customer Developer Montag, 11. Oktober 2010
- 8. A Scrum team Stakeholder ScrumMaster Stakeholder Developer Product Owner Team Customer Developer Customer Developer Montag, 11. Oktober 2010
- 9. How Scrum works Montag, 11. Oktober 2010
- 10. How Scrum works • Agile project management • Iterations („sprints“) • Framework • Inspect & Adapt Montag, 11. Oktober 2010
- 11. How Scrum works Sprint Product Product Project Sprint Product Backlog Sprint Product Potentially shippable product after each sprint Montag, 11. Oktober 2010
- 12. How Scrum works Es?mated Sprint Planning I Sprint Planning II Product Backlog Sprint Backlog regularly The Scrum Process every day Es?ma?on Mee?ng Daily Standup Retrospec?ve Review Mee?ng Mee?ng Product Backlog Montag, 11. Oktober 2010
- 13. Meetings & Artifacts Montag, 11. Oktober 2010
- 14. Product Backlog Meetings & Artifacts • Maintained by the Product Owner • Consists of user stories • Prioritized • Estimated in Estimation Meeting Montag, 11. Oktober 2010
- 15. Estimation Meeting What‘s about to come? Montag, 11. Oktober 2010
- 16. Es?ma?on Mee?ng Meetings & Artifacts • User stories estimated in storypoints • Estimated by whole team • Knowing what will come • Regularly Montag, 11. Oktober 2010
- 17. Es?ma?on Mee?ng Meetings & Artifacts Montag, 11. Oktober 2010
- 18. Sprint Planning I Setting the goal Montag, 11. Oktober 2010
- 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 written down Montag, 11. Oktober 2010
- 20. Sprint Planning II How to reach the goal Montag, 11. Oktober 2010
- 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 Montag, 11. Oktober 2010
- 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“ Montag, 11. Oktober 2010
- 23. Daily Standup Where do we stand? Montag, 11. Oktober 2010
- 24. Daily Standup Meetings & Artifacts • Same time, same place, every day! • Team sychronizes itself • Sprint Backlog is updated • Burndown Chart is updated • Public • Time for discussion afterwards Montag, 11. Oktober 2010
- 25. Daily Standup Meetings & Artifacts • What have I done since the last standup? • What will I do until the next standup? • What‘s impeding me? Montag, 11. Oktober 2010
- 26. Montag, 11. Oktober 2010
- 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 Montag, 11. Oktober 2010
- 28. Sprint Backlog Meetings & Artifacts Montag, 11. Oktober 2010
- 29. Burndown Chart Meetings & Artifacts $)# !"# !*# !$# !)# %&# %&# %&# %*# %'# %)# '*# ')# ')# (# *# )# )# )# %(+),# !)+),# )$+')# )&+')# )(+')# Montag, 11. Oktober 2010
- 30. Review Meeting Let‘s show the cake! Montag, 11. Oktober 2010
- 31. Review Mee?ng 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 Montag, 11. Oktober 2010
- 32. Review Mee?ng Meetings & Artifacts • Only completed, working software is presented • Slides are forbidden! Nobody wants to eat half-done cake or (even worse) only see an image of it ;-) The cake is not a lie! Montag, 11. Oktober 2010
- 33. Retrospective Meeting Improving the cake Montag, 11. Oktober 2010
- 34. Retrospec?ve Mee?ng 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 Montag, 11. Oktober 2010
- 35. Inspect & Adapt Montag, 11. Oktober 2010
- 36. Tweaking your improvements Montag, 11. Oktober 2010
- 37. Tweaking your improvements Rat - Maze - Experiment Experiment by Tolman & Honzik in 1930 3 groups / 17 days Montag, 11. Oktober 2010
- 38. Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' #!" +" *" )" (" !"#$%&#'($$)$*' '" ,-./0"%" &" %" $" #" !" #" $" %" &" '" (" )" *" +" #!" ##" #$" #%" #&" #'" #(" #)" +%,*' Montag, 11. Oktober 2010
- 39. Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' '#" '!" &" !"#$%&#'($$)$*' %" ,-./0"#" ,-./0"(" $" #" !" '" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*" +%,*' Montag, 11. Oktober 2010
- 40. Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' '#" '!" &" !"#$%&#'($$)$*' %" ,-./0"'" ,-./0"#" ,-./0"(" $" #" !" '" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*" +%,*' Montag, 11. Oktober 2010
- 41. Reward your team! Montag, 11. Oktober 2010
- 42. Have a BBQ! Montag, 11. Oktober 2010
- 43. Roles Montag, 11. Oktober 2010
- 44. Product Owner • Responsible for the product • Maintains the Product Backlog • Has the vision Montag, 11. Oktober 2010
- 45. Team • Self - organized • Delivers • Delivers • Delivers Montag, 11. Oktober 2010
- 46. ScrumMaster • Monitors the Scrum process • Causes course correction • Removes impediments • Protects the team Montag, 11. Oktober 2010
- 47. Impediments • Disturb the team • Hold back the team • Impediment Backlog (like Sprint Backlog) Montag, 11. Oktober 2010
- 48. Definition of Done Montag, 11. Oktober 2010
- 49. Montag, 11. Oktober 2010
- 50. Definition of Done Work in User Story To Do Done Progress TaskStory 1Task Tas TaskStory 2 TaskStory 3 Task Montag, 11. Oktober 2010
- 51. Definition of Done • Checklist • Defines when Tasks can be moved to „Done“ • Defines when User Stories can be moved to „Done“ Montag, 11. Oktober 2010
- 52. Definition of Done • Responsibility lies with the team • Maintained by the team only • Potentially shippable product every day Montag, 11. Oktober 2010
- 53. 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 Montag, 11. Oktober 2010
- 54. Definition of Done Example: DoD for User Stories – No broken unit tests – Merged into trunk • Additional criteria for specific user stories can be set in Sprint Planning I Montag, 11. Oktober 2010
- 55. Bugs Montag, 11. Oktober 2010
- 56. Bugs • Put them on your Sprint Backlog • Fix them immediately! • Fixed at best until the next daily standup • If possible: Don‘t use bugtrackers Montag, 11. Oktober 2010
- 57. Bugs Work in User Story To Do Done Progress TaskStory 1Task Tas Story 2 Task Bug Story 3 Task Task Montag, 11. Oktober 2010
- 58. Bugs &#" &!" %#" %!" $#" $!" #" !" %" &" '" #" (" )" *" +" $!" $$" $&" $'" $#" $(" $)" $*" $+" %!" %$" %%" %&" %'" %#" %(" %)" %*" %+" &!" &$" Montag, 11. Oktober 2010
- 59. Bugs 180 166,98 158,42 160 145,09 140 120 100 89,64 83,77 83,97 Stunden 80 60 50,84 52,24 37,67 40 25,6 26,73 23,57 19,04 19,87 16,29 20 11,69 10,01 0 0,67 0 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 Montag, 11. Oktober 2010
- 60. 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 Montag, 11. Oktober 2010
- 61. 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 Montag, 11. Oktober 2010
- 62. Bugs What about old Bugtracker lists? – Fix all the bugs or – Delete the list Montag, 11. Oktober 2010
- 63. Deductions Montag, 11. Oktober 2010
- 64. Deductions No upfront design constant refactoring Montag, 11. Oktober 2010
- 65. Deductions Working at the same Pair Programming user story Montag, 11. Oktober 2010
- 66. Deductions Code Reviews Pair Programming Montag, 11. Oktober 2010
- 67. Deductions Collective Code Team commitment Ownership Montag, 11. Oktober 2010
- 68. Deductions Collective Code Pair Programming Ownership Montag, 11. Oktober 2010
- 69. Deductions Fixing bugs immediately Test - Driven Nobody likes fixing bugs Development Definition of Done Montag, 11. Oktober 2010
- 70. Deductions Test - Driven Continuous Development Integration Montag, 11. Oktober 2010
- 71. Scrum at CHIP (Price comparison only) Montag, 11. Oktober 2010
- 72. Bugs per Month &,' !"#$%&&&&&&' !$' !,' !,,%' ("#""""""""' ($' (!#)(*****+' !,,)' !,(,' (,' $' ,' Montag, 11. Oktober 2010
- 73. Items per Person %*$ %&$ %)$ %($ '$ *$ &$ )$ !"#$ %&"'$ ($ +,-./$('$0$+12134$('$ +,-./$(5$0$+12134$(5$ Montag, 11. Oktober 2010
- 74. „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/ Montag, 11. Oktober 2010
- 75. Questions? Montag, 11. Oktober 2010
- 76. Literature Ken Schwaber: „Agile Project Management with Scrum“ (Microsoft Press) Montag, 11. Oktober 2010
- 77. Literature Boris Gloger: „Scrum: Produkte zuverlässig und schnell entwickeln“ (Hanser Fachbuch) Montag, 11. Oktober 2010
- 78. Literature Mike Cohn: „Succeeding with Agile: Software Development using Scrum“ (Addison-Wesley Signature) Montag, 11. Oktober 2010
- 79. We‘re hiring! Developer for price comparison and more - see www.chipxonio.de Montag, 11. Oktober 2010
- 80. Thank you! Twitter: @djungowski Blog: www.phpdevblog.net Montag, 11. Oktober 2010