Better Quality through Scrum

Dominik Jungowski, CHIP Xonio Online GmbH Better Quality through Scrum An introduction to Scrum

About me 2

About me ° 25 years old 2

About me ° 25 years old ° Working at CHIP Xonio Online GmbH 2

About me ° 25 years old ° Working at CHIP Xonio Online GmbH ° Developer and ScrumMaster for price comparison 2

About me ° 25 years old ° Working at CHIP Xonio Online GmbH ° Developer and ScrumMaster for price comparison ° Part - time studies in psychology at FernUni Hagen 2

Agenda 3

Agenda ° What is Scrum? 3

Agenda ° What is Scrum? ° How Scrum works 3

Agenda ° What is Scrum? ° How Scrum works ° Meetings, Artifacts & Roles 3

Agenda ° What is Scrum? ° How Scrum works ° Meetings, Artifacts & Roles ° Definition of Done 3

Agenda ° What is Scrum? ° How Scrum works ° Meetings, Artifacts & Roles ° Definition of Done ° Bugs 3

Agenda ° What is Scrum? ° How Scrum works ° Meetings, Artifacts & Roles ° Definition of Done ° Bugs ° Deductions 3

Agenda ° What is Scrum? ° How Scrum works ° Meetings, Artifacts & Roles ° Definition of Done ° Bugs ° Deductions ° 3 Scrum at CHIP

What is Scrum?

Scrum is... 5

Scrum is... like a recipe 5

Scrum is not... 6

A classical team 7

A classical team Stakeholder 7

A classical team Stakeholder Stakeholder 7

A classical team Stakeholder Stakeholder Customer 7

A classical team Stakeholder Stakeholder Customer Customer 7

A classical team Stakeholder Stakeholder Project manager Customer Customer 7

A classical team Stakeholder Developer Stakeholder Project manager Customer Customer 7

A classical team Stakeholder Developer Stakeholder Developer Project manager Customer Customer 7

A classical team Stakeholder Developer Stakeholder Developer Project manager Customer Developer Customer 7

A classical team Stakeholder Developer Stakeholder Developer Project manager Customer Developer Customer Developer 7

A Scrum team 8

A Scrum team Stakeholder 8

A Scrum team Stakeholder Stakeholder 8

A Scrum team Stakeholder Stakeholder Customer 8

A Scrum team Stakeholder Stakeholder Customer Customer 8

A Scrum team Stakeholder Stakeholder Product Owner Customer Customer 8

A Scrum team Stakeholder ScrumMaster Stakeholder Product Owner Customer Customer 8

A Scrum team Stakeholder ScrumMaster Stakeholder Developer Product Owner Customer Customer 8

A Scrum team Stakeholder ScrumMaster Stakeholder Developer Product Owner Customer Developer Customer 8

A Scrum team Stakeholder ScrumMaster Stakeholder Developer Product Owner Customer Developer Customer Developer 8

A Scrum team Stakeholder ScrumMaster Stakeholder Developer Product Owner Team Customer Developer Customer Developer 8

How Scrum works

How Scrum works 10

How Scrum works ° Agile project management 10

How Scrum works ° Agile project management ° Iterations („sprints“) 10

How Scrum works ° Agile project management ° Iterations („sprints“) ° Framework 10

How Scrum works ° Agile project management ° Iterations („sprints“) ° Framework ° Inspect & Adapt 10

How Scrum works 11

How Scrum works Project 11

How Scrum works Product Project Backlog 11

How Scrum works Sprint Product Project Backlog 11

How Scrum works Sprint Product Product Project Backlog 11

How Scrum works Sprint Product Product Project Sprint Backlog 11

How Scrum works Sprint Product Product Project Sprint Product Backlog 11

How Scrum works Sprint Product Product Project Sprint Product Backlog Sprint 11

How Scrum works Sprint Product Product Project Sprint Product Backlog Sprint Product 11

How Scrum works Sprint Product Product Project Sprint Product Backlog Sprint Product Potentially shippable product after each sprint 11

How Scrum works The Scrum Process Product Backlog 12

How Scrum works The Scrum Process Es8ma8on Mee8ng Product Backlog 12

How Scrum works regularly The Scrum Process Es8ma8on Mee8ng Product Backlog 12

How Scrum works Es8mated Product Backlog regularly The Scrum Process Es8ma8on Mee8ng Product Backlog 12

How Scrum works Es8mated Product Sprint Planning I Backlog regularly The Scrum Process Es8ma8on Mee8ng Product Backlog 12

How Scrum works Es8mated Product Sprint Planning I Sprint Planning II Backlog regularly The Scrum Process Es8ma8on Mee8ng Product Backlog 12

How Scrum works Es8mated Product Sprint Planning I Sprint Planning II Backlog Sprint Backlog regularly The Scrum Process Es8ma8on Mee8ng Product Backlog 12

How Scrum works Es8mated Product Sprint Planning I Sprint Planning II Backlog Sprint Backlog regularly The Scrum Process Es8ma8on Mee8ng Daily Standup Product Backlog 12

How Scrum works Es8mated Product Sprint Planning I Sprint Planning II Backlog Sprint Backlog regularly The Scrum Process every day Es8ma8on Mee8ng Daily Standup Product Backlog 12

How Scrum works Es8mated Product Sprint Planning I Sprint Planning II Backlog Sprint Backlog regularly The Scrum Process every day Es8ma8on Mee8ng Daily Standup Review Mee8ng Product Backlog 12

How Scrum works Es8mated Product Sprint Planning I Sprint Planning II Backlog Sprint Backlog regularly The Scrum Process every day Es8ma8on Mee8ng Daily Standup Retrospec8ve Review Mee8ng Mee8ng Product Backlog 12

Meetings & Artifacts

Meetings & Artifacts Product Backlog 14

Meetings & Artifacts Product Backlog ° Maintained by the Product Owner 14

Meetings & Artifacts Product Backlog ° Maintained by the Product Owner ° Consists of user stories 14

Meetings & Artifacts Product Backlog ° Maintained by the Product Owner ° Consists of user stories ° Prioritized 14

Meetings & Artifacts Product Backlog ° Maintained by the Product Owner ° Consists of user stories ° Prioritized ° Estimated in Estimation Meeting 14

Meetings & Artifacts Es8ma8on Mee8ng 15

Meetings & Artifacts Es8ma8on Mee8ng ° User stories estimated in storypoints 15

Meetings & Artifacts Es8ma8on Mee8ng ° User stories estimated in storypoints ° Estimated by whole team 15

Meetings & Artifacts Es8ma8on Mee8ng ° User stories estimated in storypoints ° Estimated by whole team ° Regularly 15

Meetings & Artifacts Sprint Planning I 16

Meetings & Artifacts Sprint Planning I ° Product Owner presents the Sprintgoal 16

Meetings & Artifacts Sprint Planning I ° Product Owner presents the Sprintgoal ° Product Owner presents the user stories 16

Meetings & Artifacts Sprint Planning I ° Product Owner presents the Sprintgoal ° Product Owner presents the user stories ° Team pulls the user stories 16

Meetings & Artifacts Sprint Planning I ° Product Owner presents the Sprintgoal ° Product Owner presents the user stories ° Team pulls the user stories ° Acceptance criteria, etc. are written down 16

Meetings & Artifacts Sprint Planning I ° Product Owner presents the Sprintgoal ° Product Owner presents the user stories ° Team pulls the user stories ° Acceptance criteria, etc. are written down ° 16 Team commits to the sprint

Meetings & Artifacts Sprint Planning II „Metaphor for this mee/ng: Design. The product development team has the chance to create the design for the solu/on they want to implement. At the end of this mee/ng, the Team knows how to build the func/onality they want to develop.“ (Scrum with Boris Gloger) 17

Meetings & Artifacts Daily Standup 18

Meetings & Artifacts Daily Standup ° Every day! 18

Meetings & Artifacts Daily Standup ° Every day! ° Team sychronizes itself 18

Meetings & Artifacts Daily Standup ° Every day! ° Team sychronizes itself ° Sprint Backlog is updated 18

Meetings & Artifacts Daily Standup ° Every day! ° Team sychronizes itself ° Sprint Backlog is updated ° Burndown Chart is updated 18

Meetings & Artifacts Daily Standup ° Every day! ° Team sychronizes itself ° Sprint Backlog is updated ° Burndown Chart is updated ° Public 18

Meetings & Artifacts Daily Standup ° Every day! ° Team sychronizes itself ° Sprint Backlog is updated ° Burndown Chart is updated ° Public ° 18 Room for discussion afterwards

Meetings & Artifacts Sprint Backlog User Story To Do Work in Progress Done Story 1 Task Task Task Story 2 Task Story 3 Task Task 19

Meetings & Artifacts Sprint Backlog User Story To Do Work in Progress Done Task Task 1 Story Task Story 2 Task Story 3 Task Task 19

Meetings & Artifacts Sprint Backlog User Story To Do Work in Progress Done Task Task 1 Story Task Task Story 2 Story 3 Task Task 19

Meetings & Artifacts Sprint Backlog User Story To Do Work in Progress Done Task Task 1 Story Task Task Story 2 Task Task Story 3 19

Meetings & Artifacts Sprint Backlog 20

Meetings & Artifacts Burndown Chart #!" '#" '!" &#" &!" %#" %!" $#" $!" #" !" !()!#)$!" !*)!#)$!" $!)!#)$!" $$)!#)$!" $%)!#)$!" $')!#)$!" $*)!#)$!" 21

Meetings & Artifacts Review Mee8ng „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) 22

Meetings & Artifacts Retrospec8ve Mee8ng 23

Meetings & Artifacts Retrospec8ve Mee8ng ° Team reflects on last sprint 23

Meetings & Artifacts Retrospec8ve Mee8ng ° Team reflects on last sprint ° „Learning from the past for the future“ 23

Meetings & Artifacts Retrospec8ve Mee8ng ° Team reflects on last sprint ° „Learning from the past for the future“ ° Output: 23

Meetings & Artifacts Retrospec8ve Mee8ng ° Team reflects on last sprint ° „Learning from the past for the future“ ° Output: ⦿ Things the Team wants to improve 23

Meetings & Artifacts Retrospec8ve Mee8ng ° Team reflects on last sprint ° „Learning from the past for the future“ ° Output: ⦿ Things the Team wants to improve ⦿ Impediments 23

Meetings & Artifacts Retrospec8ve Mee8ng ° Team reflects on last sprint ° „Learning from the past for the future“ ° Output: ⦿ Things the Team wants to improve ⦿ Impediments ° 23 Inspect & Adapt

Tweaking your improvements

Tweaking your improvements Rat - Maze - Experiment Experiment by Tolman & Honzik in 1930 3 groups / 17 days 25

Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' #!" +" *" )" (" Rat - Maze - Experiment !"#$%&#'($$)$*' '" Experiment by Tolman & Honzik in 1930 ,-./0"%" &" 3 groups / 17 days %" $" #" !" #" $" %" &" '" (" )" *" +" #!" ##" #$" #%" #&" #'" #(" #)" +%,*' 25

Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' '#" #!" +" '!" *" )" &" (" Rat - Maze - Experiment !"#$%&#'($$)$*' %" '" Experiment by Tolman & Honzik in 1930 ,-./0"#" ,-./0"%" &" 3 groups / 17 days ,-./0"(" $" %" $" #" #" !" '" #" #" $" (" %" $" &" )" '" %" (" *" )" &" *" +" '!" #!" ''" ##" '#" #$" '(" #%" '$" #&" ')" #'" '%" #(" '*" #)" +%,*' 25

Tweaking your improvements -%.*'/'0%1#'/'(23#$45#6.' '#" #!" +" '!" *" )" &" (" Rat - Maze - Experiment !"#$%&#'($$)$*' %" '" Experiment by Tolman & Honzik in 1930 ,-./0"'" ,-./0"#" ,-./0"#" ,-./0"%" &" 3 groups / 17 days ,-./0"(" ,-./0"(" $" %" $" #" #" !" '" #" #" $" (" %" $" &" )" '" %" (" *" )" &" *" +" '!" #!" ''" ##" '#" #$" '(" #%" '$" #&" ')" #'" '%" #(" '*" #)" +%,*' 25

Reward your team!

Have a BBQ!

Product Owner 29

Product Owner ° Responsible for the product 29

Product Owner ° Responsible for the product ° Maintains the Product Backlog 29

Product Owner ° Responsible for the product ° Maintains the Product Backlog ° Has the vision 29

Team 30

Team ° Self - organized 30

Team ° Self - organized ° Delivers 30

Team ° Self - organized ° Delivers ° Delivers 30

Team ° Self - organized ° Delivers ° Delivers ° Delivers 30

ScrumMaster 31

ScrumMaster ° Monitors the Scrum process 31

ScrumMaster ° Monitors the Scrum process ° Causes course correction 31

ScrumMaster ° Monitors the Scrum process ° Causes course correction ° Removes impediments 31

ScrumMaster ° Monitors the Scrum process ° Causes course correction ° Removes impediments ° Protects the team 31

Impediments 32

Impediments ° Disturb the team 32

Impediments ° Disturb the team ° Hold back the team 32

Impediments ° Disturb the team ° Hold back the team ° Impediment Backlog (like Sprint Backlog) 32

Definition of Done

Definition of Done User Story To Do Work in Progress Done TaskStory 1Task Task TaskStory 2 TaskStory 3 Task 34

Definition of Done 35

Definition of Done ° Checklist 35

Definition of Done ° Checklist ° Defines when Tasks can be moved to „Done“ 35

Definition of Done ° Checklist ° Defines when Tasks can be moved to „Done“ ° Defines when User Stories can be moved to „Done“ 35

Definition of Done 36

Definition of Done ° Responsibility lies with the team 36

Definition of Done ° Responsibility lies with the team ° Maintained by the team only 36

Definition of Done ° Responsibility lies with the team ° Maintained by the team only ° Potentially shippable product every day 36

Definition of Done Example: DoD for Tasks 37

Definition of Done Example: DoD for Tasks ⦿ Unit Tested 37

Definition of Done Example: DoD for Tasks ⦿ Unit Tested ⦿ Runs in the following browsers: Firefox, Internet Explorer, Chrome, Safari 37

Definition of Done Example: DoD for Tasks ⦿ Unit Tested ⦿ Runs in the following browsers: Firefox, Internet Explorer, Chrome, Safari ⦿ No broken unit tests 37

Definition of Done Example: DoD for Tasks ⦿ Unit Tested ⦿ Runs in the following browsers: Firefox, Internet Explorer, Chrome, Safari ⦿ No broken unit tests ⦿ Refactored 37

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 37

Definition of Done Example: DoD for User Stories 38

Definition of Done Example: DoD for User Stories ⦿ No broken unit tests 38

Definition of Done Example: DoD for User Stories ⦿ No broken unit tests ⦿ Merged into trunk 38

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 38

Bugs 40

Bugs ° Put them on your Sprint Backlog 40

Bugs ° Put them on your Sprint Backlog ° Fix them immediately! 40

Bugs ° Put them on your Sprint Backlog ° Fix them immediately! ° Fixed at best until the next daily standup 40

Bugs ° Put them on your Sprint Backlog ° Fix them immediately! ° Fixed at best until the next daily standup ° If possible: Don‘t use bugtrackers 40

Bugs User Story To Do Work in Progress Done TaskStory 1Task Task Story 2 Task Story 3 Task Task 41

Bugs User Story To Do Work in Progress Done TaskStory 1Task Task Story 2 Task Bug Story 3 Task Task 41

Bugs &#" &!" %#" %!" $#" $!" #" !" '()*+,"!%" '()*+,"!&" '()*+,"!-" '()*+,"!#" '()*+,"!." '()*+,"!/" '()*+,"!0" '()*+,"!1" '()*+,"$!" '()*+,"$$" '()*+,"$&" '()*+,"$-" '()*+,"$#" '()*+,"$." '()*+,"$/" '()*+,"$0" '()*+,"$1" '()*+,"%!" '()*+,"%$" 42

Bugs '&!" 166.98 158.42 '%!" '$!" '#!" '!!" 89.64 Stunden 83.77 83.97 &!" %!" 50.84 37.67 $!" 23.57 #!" 10.01 !" ()*+,-"'." ()*+,-"'$" ()*+,-"'/" ()*+,-"'%" ()*+,-"'0" ()*+,-"'&" ()*+,-"'1" ()*+,-"#!" ()*+,-"#'" 43

Bugs !"#$%&%'()*+,)-.(% !!"!!$# !!"!!$# !!"!!!# !!"!!!# !!"!!!# !!"!!!# !!"!!!# %&'()*#!+# %&'()*#!,# %&'()*#!-# %&'()*#$$# %&'()*#$,# %&'()*#$-# %&'()*#+$# 44

Bugs Example: DoD for Bugs 45

Bugs Example: DoD for Bugs ⦿ Unit tested 45

Bugs Example: DoD for Bugs ⦿ Unit tested ⦿ No broken unit tests 45

Bugs Example: DoD for Bugs ⦿ Unit tested ⦿ No broken unit tests ⦿ Fixed in the following browsers: Firefox, Internet Explorer, Chrome, Safari 45

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 45

Bugs 46

Bugs What about old Bugtracker lists? 46

Bugs What about old Bugtracker lists? ⦿ Fix all the bugs or 46

Bugs What about old Bugtracker lists? ⦿ Fix all the bugs or ⦿ Delete the list 46

Deductions

Deductions 48

Deductions No upfront design 48

Deductions No upfront design constant refactoring 48

Deductions 49

Deductions Working at the same user story 49

Deductions Working at the same Pair Programming user story 49

Deductions 50

Deductions Code Reviews 50

Deductions Code Reviews Pair Programming 50

Deductions 51

Deductions Team commitment 51

Deductions Team commitment Collective Ownership 51

Deductions 52

Deductions Fixing bugs immediately 52

Deductions Fixing bugs immediately Nobody likes fixing bugs 52

Deductions Fixing bugs immediately Nobody likes fixing bugs Definition of Done 52

Deductions Fixing bugs immediately Test - Driven Nobody likes fixing bugs Development Definition of Done 52

Deductions 53

Deductions Test - Driven Development 53

Deductions Test - Driven Continuous Development Integration 53

Scrum at CHIP (Price comparison only)

Bugs per Month &,' !"#$%&&&&&&' !$' !,' ($#$' !,,%' ($' (!#)(*****+' !,,)' !,(,' (,' $' ,' 55

Items per Person %*$ %&$ %)$ %($ '$ *$ &$ )$ !"#$ %&"'$ ($ +,-./$('$0$+12134$('$ +,-./$(5$0$+12134$(5$ 56

„Companies, managers should understand, that their employees want to work. Trust them, that they want to do a good job.“ h"p://feedproxy.google.com/~r/borisgloger-‐de/~3/U2zztp7jcW8/

Questions?

Literature Ken Schwaber: „Agile Project Management with Scrum“ (Microsoft Press) 59

Literature Boris Gloger: „Scrum: Produkte zuverlässig und schnell entwickeln“ (Hanser Fachbuch) 60

Literature Mike Cohn: „Succeeding with Agile: Software Development using Scrum“ (Addison-Wesley Signature) 61

We‘re hiring! Developer for price comparison (and more - see www.chipxonio.de)

Thank you! Twitter: @djungowski Blog: www.phpdevblog.net

http://www.phpdevblog.net	1788
http://phpdevblog.net	80
http://www.slideshare.net	25
http://phpdevblog.niknovo.com	19
http://translate.googleusercontent.com	4
http://admin.totalmarketing.com	2
http://perevod.yandex.net	1
http://clickwatchlearn.blogspot.com	1

Better Quality through Scrum

by Dominik Jungowski on Jun 01, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

8 Embeds 1,920

Statistics

Better Quality through Scrum — Presentation Transcript