2. 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
3. Agenda
What
is
Scrum?
How
Scrum
works
MeeDngs,
ArDfacts
&
Roles
DefiniDon
of
Done
Bugs
DeducDons
Scrum
at
CHIP
10. How Scrum works
Agile
project
management
IteraDons
(„sprints“)
Framework
Inspect
&
Adapt
11. How Scrum works
Sprint Product
Product
Project Sprint Product
Backlog
Sprint Product
Potentially shippable product after each sprint
12. How Scrum works
EsDmated
Sprint
Planning
I Sprint
Planning
II
Product
Backlog
Sprint
Backlog
regularly
The Scrum Process every day
EsDmaDon
MeeDng Daily
Standup
RetrospecDve
Review
MeeDng
MeeDng
Product
Backlog
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
wriZen
down
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
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“
24. Daily
Standup
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
25. Daily
Standup
Meetings & Artifacts
What
have
I
done
since
the
last
standup?
What
will
I
do
unDl
the
next
standup?
What‘s
impeding
me?
26.
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
32. Review
MeeDng
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
37. RetrospecDve
MeeDng
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
53. Definition of Done
Work in
User Story To Do Done
Progress
TaskStory
1Task
Tas
TaskStory
2
TaskStory
3
Task
54. Definition of Done
Checklist
Defines
when
Tasks
can
be
moved
to
„Done“
Defines
when
User
Stories
can
be
moved
to
„Done“
55. Definition of Done
Responsibility
lies
with
the
team
Maintained
by
the
team
only
PotenDally
shippable
product
every
day
56. 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
57. 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
65. 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
78. „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/