better quality through scrum (2011)
DESCRIPTION
2011 Edition of my Better Quality through Scrum sessionTRANSCRIPT
Dominik Jungowski | CHIP Xonio Online GmbH
Better Quality through Scrum
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
What is Scrum?
How Scrum works
MeeDngs, ArDfacts & Roles
DefiniDon of Done
Bugs
DeducDons
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
IteraDons („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
EsDmaDonMeeDng
EsDmated Product Backlog
Sprint Planning I Sprint Planning II
Daily Standup
Review MeeDngRetrospecDve MeeDng
Sprint Backlog
Meetings & Artifacts
Meetings & Artifacts
Maintained by the Product Owner
Consists of user stories
PrioriDzed
EsDmated in EsDmaDon MeeDng
Product Backlog
Estimation MeetingWhat‘s about to come?
Meetings & Artifacts
User stories esDmated in storypoints
EsDmated by whole team
Knowing what will come
Regularly
EsDmaDonMeeDng
Meetings & Artifacts
EsDmaDonMeeDng
Sprint Planning ISetting the goal
Meetings & Artifacts
Product Owner presents the Sprintgoal
Product Owner presents the user stories
Team pulls the user stories
Acceptance criteria, etc. are wriZen down
Sprint Planning I
Sprint Planning IIHow to reach the goal
Meetings & Artifacts
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
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“
Sprint Planning II
Daily StandupWhere do we stand?
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
Daily Standup
Meetings & Artifacts
What have I done since the last standup?
What will I do unDl the next standup?
What‘s impeding me?
Daily Standup
Meetings & Artifacts
Sprint Backlog
User Story To DoWork in Progress
Done
Task
Task Task Task
Task Task
Story 1
Story 2
Story 3
Meetings & Artifacts
Sprint Backlog
Meetings & Artifacts
Sprint Backlog
Meetings & Artifacts
Burndown Chart
!"#
!$#
%&# %&# %&#
%'#
(#
')#
)# )#
)#
*#
')#
'*#
%)#
%*#
!)#
!*#
$)#
%(+),# !)+),# )$+')# )&+')# )(+')#
Review MeetingLet‘s show the cake!
Meetings & Artifacts
Review MeeDng
„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
Meetings & Artifacts
Only completed, working so_ware is presented
No slides!
Review MeeDng
The cake is not a lie!
Review MeeDng
Retrospective MeetingImproving the cake
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
RetrospecDve MeeDng
Inspect & Adapt
Tweaking your improvements
Rat - Maze - ExperimentExperiment by Tolman & Honzik in 1930
3 groups / 17 days
Tweaking your improvements
!"
#"
$"
%"
&"
'"
("
)"
*"
+"
#!"
#" $" %" &" '" (" )" *" +" #!" ##" #$" #%" #&" #'" #(" #)"
!"#$%&#'($$)$*'
+%,*'
-%.*'/'0%1#'/'(23#$45#6.'
,-./0"%"
Tweaking your improvements
!"
#"
$"
%"
&"
'!"
'#"
'" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*"
!"#$%&#'($$)$*'
+%,*'
-%.*'/'0%1#'/'(23#$45#6.'
,-./0"#"
,-./0"("
Tweaking your improvements
!"
#"
$"
%"
&"
'!"
'#"
'" #" (" $" )" %" *" &" +" '!" ''" '#" '(" '$" ')" '%" '*"
!"#$%&#'($$)$*'
+%,*'
-%.*'/'0%1#'/'(23#$45#6.'
,-./0"'"
,-./0"#"
,-./0"("
Tweaking your improvements
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 correcDon
Removes impediments
Protects the team
Impediments
Disturb the team
Hold back the team
Impediment Backlog (like Sprint Backlog)
Definition of Done
Definition of Done
User Story To DoWork in Progress
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
PotenDally 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
No broken unit tests
Merged into trunk
AddiDonal 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 unDl the next daily standup
If possible: Don‘t use bugtrackers
Bugs
User Story To DoWork in Progress
Done
Task
Task Tas Task
Task Task
Story 1
Story 2
Story 3
Bug
Meetings & Artifacts
Sprint Backlog
Bugs
!"
#" #"
$$"
$!"
%"
$$"
$&"
%"
!"
#"
'"
#"
("
)"
$"
*"
#" #"
("
$+"
%"
("
$&"
%"
'"
#"
'"
#"
("
)"
'"
&"
#"
!"
+"
)"
$&"
$#"
$!"
$+"
$)"
'&" '$" '#" ''" '!" '*" '+" '%" ')" '(" !&" !$" !#" !'" !!" !*"
!"#$%&'
19,87
0,67
6,56
33,22
52,32 48,07
90,64
82,33
66,95
7,87
57,39
44,23
17,03 15,27
29,26
7,23
0
10
20
30
40
50
60
70
80
90
100
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
Stu
nden
!"#$%&'
Bugs
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
No broken unit tests
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/
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!
Thank you!
Twitter: @djungowskiBlog: www.phpdevblog.net