Better Quality through Scrum

Dominik Jungowski | CHIP Xonio Online GmbH

Better Quality through Scrum

Montag, 11. Oktober 2010

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


• What is Scrum?

• How Scrum works

• Meetings, Artifacts & Roles

• Definition of Done

• Bugs

• Deductions

• Scrum at CHIP

Agenda


What is Scrum?


Scrum is...

like a recipe


Scrum is not...


A classical team

Project manager

Stakeholder

Customer

Stakeholder

Customer

Developer

Developer

Developer

Developer


A Scrum team

Product Owner

Stakeholder

Customer

Stakeholder

Customer

ScrumMaster

Developer

Developer

Developer

Team


How Scrum works


How Scrum works

• Agile project management

• Iterations („sprints“)

• Framework

• Inspect & Adapt


How Scrum works

ProjectProduct Backlog

Sprint Product

Sprint Product

Sprint Product

Potentially shippable product after each sprint


every dayregularly The Scrum Process

How Scrum works

Product Backlog

Es?ma?onMee?ng

Es?mated Product Backlog

Sprint Planning I Sprint Planning II

Daily Standup

Review Mee?ngRetrospec?ve Mee?ng

Sprint Backlog


Meetings & Artifacts



• Maintained by the Product Owner

• Consists of user stories

• Prioritized

• Estimated in Estimation Meeting

Product Backlog


Estimation MeetingWhat‘s about to come?



• User stories estimated in storypoints

• Estimated by whole team

• Knowing what will come

• Regularly

Es?ma?onMee?ng



Es?ma?onMee?ng


Sprint Planning ISetting the goal



• Product Owner presents the Sprintgoal

• Product Owner presents the user stories

• Team pulls the user stories

• Acceptance criteria, etc. are written down

Sprint Planning I


Sprint Planning IIHow to reach the goal


Meetings & ArtifactsSprint Planning II

„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



• 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“

Sprint Planning II


Daily StandupWhere do we stand?



• Same time, same place, every day!

• Team sychronizes itself

• Sprint Backlog is updated

• Burndown Chart is updated

• Public

• Time for discussion afterwards

Daily Standup



• What have I done since the last standup?

• What will I do until the next standup?

• What‘s impeding me?

Daily Standup



Meetings & ArtifactsSprint Backlog

User Story To DoWork in Progress

Done

Task

Task Task Task

Task Task

Story 1

Story 2

Story 3


Meetings & ArtifactsSprint Backlog


Meetings & ArtifactsBurndown Chart

!"#

!$#

%&# %&# %&#

%'#

(#

')#

)# )#

)#

*#

')#

'*#

%)#

%*#

!)#

!*#

$)#

%(+),# !)+),# )$+')# )&+')# )(+')#


Review MeetingLet‘s show the cake!


Meetings & ArtifactsReview Mee?ng

„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



• 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!

Review Mee?ng


Retrospective MeetingImproving the cake



• Team reflects on last sprint

• „Learning from the past for the future“

• Output:

– Things the Team wants to improve

– Impediments

• Similar to a debriefing

Retrospec?ve Mee?ng


Inspect & Adapt


Tweaking your improvements


Rat - Maze - ExperimentExperiment by Tolman & Honzik in 1930

3 groups / 17 days



!"

#"

$"

%"

&"

'"

("

)"

*"

+"

#!"

#" $" %" &" '" (" )" *" +" #!" ##" #$" #%" #&" #'" #(" #)"

!"#$%&#'($$)$*'

+%,*'

-%.*'/'0%1#'/'(23#$45#6.'

,-./0"%"



!"

#"

$"

%"

&"

'!"

'#"

'" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*"

!"#$%&#'($$)$*'

+%,*'

-%.*'/'0%1#'/'(23#$45#6.'

,-./0"#"

,-./0"("



!"

#"

$"

%"

&"

'!"

'#"

'" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*"

!"#$%&#'($$)$*'

+%,*'

-%.*'/'0%1#'/'(23#$45#6.'

,-./0"'"

,-./0"#"

,-./0"("



Reward your team!


Have a BBQ!


Roles


Product Owner

• Responsible for the product

• Maintains the Product Backlog

• Has the vision


Team

• Self - organized

• Delivers

• Delivers

• Delivers


ScrumMaster

• Monitors the Scrum process

• Causes course correction

• Removes impediments

• Protects the team


Impediments

• Disturb the team

• Hold back the team

• Impediment Backlog (like Sprint Backlog)


Definition of Done



Definition of Done


Done

Task

Task Tas Task

Task Task

Story 1

Story 2

Story 3


Definition of Done

• Checklist

• Defines when Tasks can be moved to „Done“

• Defines when User Stories can be moved to „Done“


Definition of Done

• Responsibility lies with the team

• Maintained by the team only

• Potentially shippable product every day


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


Definition of Done

Example: DoD for User Stories


– Merged into trunk

• Additional criteria for specific user stories can be set in Sprint Planning I


Bugs


Bugs

• Put them on your Sprint Backlog

• Fix them immediately!

• Fixed at best until the next daily standup

• If possible: Don‘t use bugtrackers


Bugs


Done

Task

Task Tas Task

Task Task

Story 1

Story 2

Story 3

Bug


Bugs

!"

#"

$!"

$#"

%!"

%#"

&!"

&#"

%" &" '" #" (" )" *" +" $!" $$" $&" $'" $#" $(" $)" $*" $+" %!" %$" %%" %&" %'" %#" %(" %)" %*" %+" &!" &$"


Bugs

166,98

10,01

83,77

158,42

50,84

83,97 89,64

23,57

37,67

52,24

16,29 19,04

0

25,6

11,69

145,09

26,73 19,87

0,67 0

20

40

60

80

100

120

140

160

180

13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

Stu

nden


Bugs

00.000

00.000

00.000

00.000

00.000

00.001

00.001

2 5 8 11 15 18 21 24 27 30

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


Bugs

Example: DoD for Bugs

– Unit tested


– Fixed in the following browsers: Firefox, Internet Explorer, Chrome, Safari

– Distributed to all web servers


Bugs

What about old Bugtracker lists?

– Fix all the bugs or

– Delete the list


Deductions


Deductions

No upfront design constant refactoring


Deductions

Working at the sameuser story Pair Programming


Deductions

Code Reviews Pair Programming


Deductions

Team commitment Collective Code Ownership


Deductions

Pair Programming Collective Code Ownership


Deductions

Nobody likes fixing bugs Test - DrivenDevelopment

Definition of Done

Fixing bugs immediately


Deductions

Test - DrivenDevelopment

ContinuousIntegration


Scrum at CHIP(Price comparison only)


Bugs per Month

!"#$%&&&&&&'

(!#)(*****+'("#""""""""'

,'

$'

(,'

($'

!,'

!$'

&,'

!,,%'

!,,)'

!,(,'


Items per Person

!"#$ %&"'$($

)$

&$

*$

'$

%($

%)$

%&$

%*$

+,-./$('$0$+12134$('$ +,-./$(5$0$+12134$(5$


„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/


http://feedproxy.google.com/~r/borisgloger-de/~3/U2zztp7jcW8/

http://feedproxy.google.com/~r/borisgloger-de/~3/U2zztp7jcW8/

Questions?


LiteratureKen Schwaber: „Agile Project Management with Scrum“

(Microsoft Press)


LiteratureBoris Gloger: „Scrum: Produkte zuverlässig und schnell entwickeln“

(Hanser Fachbuch)


LiteratureMike Cohn: „Succeeding with Agile: Software Development using Scrum“

(Addison-Wesley Signature)


Developer for price comparisonand more - see www.chipxonio.de

We‘re hiring!


http://www.chipxonio.de

http://www.chipxonio.de

Thank you!

Twitter: @djungowskiBlog: www.phpdevblog.net


http://www.phpdevblog.net

http://www.phpdevblog.net

Technology

Better Quality through Scrum