28. 1
:
Release
planning
to
release
product
increments
2
:
Iteradon
planning
meedng
3
:
Iteradon
4
:
Planning
poker
to
esdmate
tasks
during
sprint
planning
5
:
The
project
velocity
is
measured
6
:
Short
daily
meedng
to
resolve
current
issues
7
:
sprint
retrospecdve
to
learn
from
previous
sprint
8
:
Kanban
9
:
Sprint
review
meedng
to
present
completed
work
10
:
Task
board(Task
card)
11
:
Burn
down
chart
to
monitor
sprint
progress
12
:
Flexible
process
13
:
User
stories
are
wri?en
14
:
Mutual
commitment
to
sprint
backlog
between
product
owner
and
team
15
:
Incepdon
Deck
16
:
Priorides
(product
backlog)
maintained
by
a
dedicated
role
(product
owner)
17
:
Rapid
feedback
18
:
Pair
Programming
19
:
Automated
regression
test
20
:
Test
Driven
Develpment
21
:
Unit
Test
Automadon
22
:
Acceptance
tests
are
run
onen
and
the
score
is
published
23
:
System
Metaphor
24
:
Spike
Soludon
25
:
Constant
refactoring
26
:
Simple
Design
27
:
Only
one
pair
integrates
code
at
a
dme
28
:
Condnuous
Integradon
29
:
Use
collecdve
ownership
30
:
Code
wri?en
to
agreed
standards
31
:
When
a
bug
is
found,
tests
are
created
32
:
Analog
Tools
33
:
Customer
Proxy
34
:
The
customer
is
always
available
35
:
Product
Owner
36
:
Development
process
and
pracdces
facilitated
by
a
dedicated
role
(Scrum
master)
37
:
Agile
Coach
38
:
Team
members
volunteer
for
tasks
(self-‐organizing
team)
39
:
Niko-‐niko
Calendar
(Smiley
Calendar)
40
:
Set
a
sustainable
pace
41
:
Right
agile
style
for
their
organizadon
42
:
Give
the
team
a
dedicated
open
work
space
43
:
One
whole
team
44
:
Move
people
around
45
:
Set
up
a
dedicated
integradon
computer
46
:
User
Story
Mapping
47
:
Definidon
of
DONE
48
:
Fun
is
important
49
:
Slacking
Organizadonal
Structure
Network
of
Referred
Pracdces
as
a
Pa?ern
Language
1
23
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
2930
31
32
33
34
35
36
37
38
39
40
41
42 43
44
45
46
47
48
49
CultureWorks,
LLC