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


Agenda
• What is Scrum?

• How Scrum works

• Meetings, Artifacts & Roles

• Definition of Done

• Bugs

• Deductions

• Scrum at CHIP


What is Scrum?


Scrum is...

like a recipe


Scrum is not...


A classical team

Stakeholder Developer

Project
manager
Customer Developer

Customer Developer


A Scrum team

Stakeholder ScrumMaster

Product
Owner

Team
Customer Developer

Customer Developer


How Scrum works


How Scrum works
• Agile project management

• Iterations („sprints“)

• Framework

• Inspect & Adapt


How Scrum works

Sprint Product

Product

Project Sprint Product
Backlog

Sprint Product

Potentially shippable product after each sprint

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


Meetings & Artifacts


Product
Backlog

• Maintained by the Product Owner

• Consists of user stories

• Prioritized

• Estimated in Estimation Meeting


Estimation
Meeting
What‘s about to come?


Es?ma?on
Mee?ng

• User stories estimated in storypoints

• Estimated by whole team

• Knowing what will come

• Regularly


Es?ma?on
Mee?ng



Sprint Planning I
Setting the goal


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


Sprint Planning II
How to reach the goal


Sprint
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


Sprint
Planning
II

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


Daily Standup
Where do we stand?


Daily
Standup

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


Sprint
Backlog

Work in
User Story To Do Done
Progress

Story
1 Task Task Task

Story
2 Task

Story
3 Task Task


Sprint
Backlog



Burndown
Chart

$)#
!"#

!*# !$#

!)#
%&# %&# %&#

%*#
%'#

%)#

'*#

')#
')# (#

*#

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


Review Meeting
Let‘s show the cake!


Review
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


Review
Mee?ng

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


Retrospective Meeting
Improving the cake


Retrospec?ve

Mee?ng

• Team reflects on last sprint

• „Learning from the past for the future“

• Output:
– Things the Team wants to improve

– Impediments

• Similar to a debriefing


Inspect & Adapt


Tweaking your
improvements


Tweaking your improvements

Rat - Maze - Experiment
Experiment 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
Work in
Progress

TaskStory
1Task
Tas

TaskStory
2

TaskStory
3
Task


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
Work in
Progress

TaskStory
1Task
Tas

Story
2 Task Bug

Story
3 Task Task


Bugs
&#"

&!"

%#"

%!"

$#"

$!"

#"

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


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


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


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 same
Pair Programming
user story


Deductions

Code Reviews Pair Programming


Deductions

Collective Code
Team commitment
Ownership


Deductions

Collective Code
Pair Programming
Ownership


Deductions

Fixing bugs immediately

Test - Driven
Nobody likes fixing bugs
Development

Definition of Done


Deductions

Test - Driven Continuous
Development Integration


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/


Questions?


Literature
Ken Schwaber: „Agile Project
Management with Scrum“

(Microsoft Press)


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

(Hanser Fachbuch)


Literature
Mike Cohn: „Succeeding with
Agile: Software Development
using Scrum“

(Addison-Wesley Signature)


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


Thank you!

Twitter: @djungowski
Blog: www.phpdevblog.net

Better Quality through Scrum

Recommended

Recommended

More Related Content

Similar to Better Quality through Scrum

Similar to Better Quality through Scrum (20)

More from Dominik Jungowski

More from Dominik Jungowski (20)

Recently uploaded

Recently uploaded (20)

Better Quality through Scrum