Little book of Scrum

Scrum quick view

Scrum&Mee)ng&

Timebox&&
(Maximum&length)&

A8endees&

Sprint'Planning'part'I'

1"month:"4"hrs"
2"weeks:"2"hrs"

Product"Owner"
Team"Members"
ScrumMaster"

Sprint'Planning'part'II'

1"month:"4"hrs"
2"weeks:"2"hrs"

Team"Members"
ScrumMaster"
Product"Owner"(reachable"if"not"present)"

Daily'Scrum'

1"month:"15"minutes"
2"weeks:"15"minutes"

Team"Members"
ScrumMaster"
Product"Owner"(OpAonal)"

Product'Backlog'Renement'

10%"of"the"Sprint"capacity"

Product"Owner"
Team"Members"
ScrumMaster"

Sprint'Review'

1"month:"4"hrs"
2"weeks:"2"hrs"

Product"Owner"
Team"Members"
ScrumMaster"
Interested"Stakeholders"

Sprint'Retrospec<ve'

1"month:"3"hrs"
2"weeks:"1.5"hrs"

Product"Owner"
Team"Members"
ScrumMaster"
2

"
Scrum"is"an"Agile"framework&&
to"develop&products&and"organise&work.&&&
Daily&&
Scrums&
Product&Backlog&
Renement!

Build"
Test"
Adapt"

Product&&
Owner&

Product&&
Backlog&

Sprint:"

Sprint&&
Review&

Sprint&&
Retrospec)ve&
Sprint&&
Planning&

Agile"was"rst&used&to&build&soHware,"but"
`!
is"now"used"for"everything"from"running"a"
sales"team"to"planning"a"wedding."

Scrum"builds"products"in"less"than"30"day"increments."
It"was"designed"for"complex&to&simple&product"
development."
&

""Short"cycles"create&fast&feedback,&builds&in&quality"
and"lets"you"release"batches"iteraAvely,"which"equals"
more&value&sooner.&&&
Build
Test
Adapt
Build
Test
Adapt
Build
Test
Adapt

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Delivered&
Value&

Build
Test
Adapt
Build
Test
Adapt

Delivered&
Value&

Delivered&
Value&

Scrum"ts"under"the&Agile&umbrella&which""
includes"other"lightweight"methodologies."
"

It"was"designed"based&on&research&of"the"most"
successful"processes"used"in"IBM,&Xerox&and"the"
Japanese&car&industry.""
6

"""
All"of"these"lightweight&approaches&
are"driven"by"a&common&set&of&
`!
principles&and&values"called"the"
Agile&Manifesto.&

THE&AGILE&MANIFESTO&
&

Individuals&and&interac)ons&over"processes"and"tools"
Working&soHware&over"comprehensive"documentaAon"
Customer&collabora)on&over"contract"negoAaAon"
Responding&to&change&over"following"a"plan"

While"there&is&value&in&the&items&on&the&right,"we"
value"the"items"on"the"leQ"more."
(see"agilemanifesto.org)"
"
7"

Agile"Manifesto"Principles"S"I&
1."Our"highest"priority"is"to"saAsfy"the"customer"through"early&and&
con)nuous&delivery"of"valuable"soQware."
"

2."Welcome&changing&requirements,"even"late"in"development."Agile"
processes"harness"change"for"the"customer's"compeAAve"advantage."

"""

The"Agile"methods"
follow""12&core&
principles&
!

"

3."Deliver&working&soHware&frequently,"from"a"couple"of"weeks"to"a"
couple"of"months,"with"a"preference"to"the"shorter"Amescale."
"

4."Business&people&and&developers&must&work&together&daily"
throughout"the"project."
"

5."Build&projects&around&mo)vated&individuals."Give"them"the"
environment"and"support"they"need,"and"trust"them"to"get"the"job"
done."
"

6."The"most"ecient"and&eec)ve&method&of&conveying&informa)on"
to"and"within"a"development"team"is&face[to[face&conversa)on.&
"
8"

Agile"Manifesto"Principles"S"II&
"
7."Working&soHware&is&the&primary&measure&of&progress.&
"

8."Agile&processes&promote&sustainable&development.&The"
sponsors,"developers,"and"users"should"be"able"to"maintain"a"
constant"pace"indenitely."
"

9."ConAnuous"a8en)on&to&technical&excellence&and&good&
design&enhances"agility."
"

10."Simplicity"S"the"art"of"maximizing"the"amount"of"work"not"
done"S"is"essenAal."
"

11."The"best"architectures,"requirements,"and"designs"emerge"
from"self[organizing&teams."
"

12."At"regular"intervals,"the&Team&reects&on&how&to&become&
more&eec)ve,"then"tunes"and"adjusts"its"behavior"
accordingly."
9"

Product Vision
We"need"to"have"a"
vision"to"guide"the"
team"and"ensure"
successful"outcomes.&

"Vision&
Clear"and"inspiraAonal"direcAon""
for"the"product"

10

Here is an example of a product vision:

oBy!the!end!of!Q4,!our!online!bookstore!will!
allow!customers!to!purchase!books!easily!
with!fast,!quality!delivery.!

11

Scrum relies on having a good Team with all

the cross-functional skills needed to deliver
end-to-end product increments.
A Scrum Team ranges from 2-9 people and
includes the Product Owner, ScrumMaster
and Development Team.

12

"

"""

Team&Members&
We"are"a"cross[func)onal&team&and""
gure"out"how"to"do"our"work."We"
`"
are"self[managing&and&self[
organising.&&&

ScrumMaster&
I"am"responsible"for"the"
`!
Team"and"OrganisaAon"
adop)ng&Scrum&successfully."""&

'
Product&Owner'
I"am"responsible"for"managing&
`!
the&Product&Backlog&and"overall"
product&success.'

13

Each&Sprint&includes"some&planning,&design,&
development&and&tes)ng&and"is"done"in&
parallel,&which"is"why"the"Team"needs"crossS
funcAonal"skillsets"to"deliver"a"complete"
product"increment"at"the"end"of"each"Sprint."""
&

Plan
Design
Test =
Build
14

You"can"choose&a&Sprint&length&as"long"as"it"is"
less&than&one&month.""Two&week&Sprints&are"one"
of"the"most&common"lengths.""Each"Scrum"
meeAng"gets"adjusted"in"proporAon"to"the"
length"chosen."
&

One&Month&Sprint&

Two&week&Sprint&

Sprint&Planning&1"

4"hours"

Sprint&Planning&1"

2"hours"

Sprint&Planning&2"

4"hours"

Sprint&Planning&2"

2"hours"

Daily&Scrums"

<"15"minutes"

Daily&Scrums"

<"15"minutes"

Product&Backlog&
Renement"

10%"of"Sprint"capacity"

Product&Backlog&
renement"

10%"of"Sprint"capacity"

Sprint&Review"

3"hours"

Sprint&Review"

1.5"hours"

Sprint&Retrospec)ve"

4"hours"

Sprint&Retrospec)ve"

2"hours"

15

We"set&the&rst&and&last&day&of"the"Sprint"and"
run"them"backStoSback"with"no"gaps"between."""
&

All&of&the&Scrum&Mee)ngs&are&included&
within"the"Sprint."

Daily&&
Scrums&
Product&Backlog&
Renement!

Sprint&&
Review&
!

Sprint

Sprint&&
Retrospec)ve&
Sprint&&
Planning&

16

16

Scrum"has"four"core"mee)ngs&
Sprint&Planning"

A"twoSpart"meeAng"to"plan"the"upcoming"Sprints"work.""
Each"part"takes"up"to"four"hours"for"a"one"month"sprint"
(halve"this"for"a"two"week"Sprint)"

Sprint&Review&

Daily&Scrum&

A"daily"15"minute"meeAng"for"the"
Development"Team"to"discuss"progress"and"
raise"issues"to"get"resolved."

Sprint&Retrospec)ve"
"

MeeAng"to"review"the"product"and"get"
feedback"on"what"the"Team"has"
delivered"in"the"previous"Sprint."

MeeAng"to"inspect"and"adapt"the"
process"and"improve"the"way"the"Scrum"
Team"works."

1"hr"per"week"of"Sprint""
(4"hrs"for"a"one"month"Sprint)"

45"minutes"per"week"of"Sprint""
(3"hrs"for"a"one"month"Sprint)"

"

"

17

Its"a"good"idea"to"book&the&Scrum&Mee)ngs&in&advance"and"
secure"meeAng"areas.""The"key"meeAngs"to"setup"are:"
"

Sprint&Planning&1&
Sprint&Planning&2&
Daily&Scrums&
Product&Backlog&renement&
Sprint&Review&
Sprint&Retrospec)ve&
"

18

Sprint"Planning"part"1"
In&Sprint&Planning&part&1&
the"Scrum"Team"sets"the"
Sprint"Goal"and"the"
Development"Team"selects"
a"porAon"of"the"Product"
Backlog.&

ATTENDEES:&
! Product"Owner"
! ScrumMaster"
! Development"Team"
&

INPUTS:&
! Product"Backlog"
TIMEBOX:"
! 1"hour"per"week"of"Sprint""
"(4"hrs"for"a"one"month"Sprint)"
"

OUTPUT:"
! Sprint"Goal"
! Product"Backlog"Items"selected"
based"on"eort"esAmate&

Sprint&&
Goal&
"

Selected&
Product&
Backlog&
"

Product&
Backlog&
"
19

Sprint"Planning"Part"2"
In&Sprint&Planning&part&2&the"
Development"Team"breaks"
the"Product"Backlog"Items"
into"tasks"and"works"out"
how"they"will"deliver"the"
Sprint"Goal.!

ATTENDEES:&
! Development"Team"
! ScrumMaster"
! Product"Owner"(reachable"if"not"
present)"
&
INPUTS:"
! Product"Backlog"Items"
TIMEBOX:"
! 1"hour"per"week"of"Sprint"
"(4"hrs"for"a"one"month"Sprint)"
OUTPUTS:"
! Sprint"Backlog"

The"Sprint&Backlog&is"the"subset"of"
the"Product"Backlog"we"produce"
during"planning,"and"work"on"during"
a"Sprint.&
Selected&
Product&
Backlog&
"

Write failing
test
Write form
validation

Write
server-side
logic

Create DB
schema

Do GUI
design

Do
integration
test

Sprint"Backlog"
"

20

We"create"the"tasks"and"decide"who"does"
what.""We"choose"what"we"work"on"and"how"
!!
much"we"can"take"into"a"Sprint.""This"
moAvates"us"as"our"esAmates"are"far"more"
realisAc"and"achievable.!

Product"Backlog"
Item"
As a travel agent I
want to run
Ona
back
report on the
latest flight deals

Design UI

Create HTML
form
Run usability
tests

Write online
help

Update
security tests

Refactor DB
reports for
data
warehouse

Write serverside logic

Configure
collector for
new tables

Broken"down"into"tasks"
by"the"team"

21

Product"Backlog"Item"

S"Tasks&are&es)mated&in&hours,"approximately"1S16"hours"
each."
S"Team&Members&sign&up&for&tasks,&they&arent&assigned&
S"EsAmated"work"remaining"is"updated&daily&&
S"Any&Team&Member&can"add,"delete"or"change"the"Sprint"
Backlog"(theirs"or"new)""

22

Daily"Scrum"

23

Daily"Scrum"
The"Daily"Scrum"is"a"short"daily"
meeAng"for"the"Team"Members"to"
update&each&other&on&progress&and&
resolve&any&impediments&blocking"
them"from"achieving"the"Sprint"
Goal."""

ATTENDEES:&
! Team"Members"
! ScrumMaster"
! Product"Owner"(opAonal)"
! Interested"stakeholders"(opAonal)"
&
INPUTS:&
! Impediments"
! Team"Members"progress"
TIMEBOX:"
! Maximum"of"15"minutes"per"day"
OUTPUT:"
! Updated"Scrum"Board"
! Updated"Burndown"Chart"
! Updated"Sprint"Backlog"

24

Daily"Scrum"
We&speak&to&each&other,"not"the"Scrum"
Master"or"a"manager.""Other"people"can"
afend"but"only&the&Scrum&Team&can&speak&
unless"we"want"to"ask"a"stakeholder"a"
quesAon.""

We"answer"3"quesAons:"
1."What&has&been&accomplished"since"the"
last"meeAng?"
2."What&we&will&work&on&next&&&
3."What&blocks&are&in&our&way&and"needs"to"
be"resolved?"

We"hold"our"meeAng"at"the&
same&)me&and&place&each&
day,"and"we"like"to"stand"up"
so"it"nishes"on"Ame!""""

25

Daily"Scrum"Tips"
I"book"the"meeAng"room"early"and"if"possible,"
get"the"Scrum"Board"or"at"least"the"Sprint"
Burndown"so"the"Team"can"view"them"easily.""
For"Team"Members"who"cant"physically"be"in"
the"meeAng,"they"can"call"in"or"send"their"
update"if"they"are"away."

I"nd"it"helps"to"book"the"room"for"an"extra"15"minutes"so"the"
team"can"discuss"any"inSdepth"issues"aQer"the"Daily"Scrum.""
"

The"hardest"thing"for"me"as"the"ScrumMaster"is"to"get"the"
Team"to"talk"to"each"other,"instead"of"reporAng"to"me.""I"have"
to"look"away"or"step"back"from"the"circle"to"stop"this"
happening"someAmes.""

26

Product"Backlog"Renement"
8!
3!

27

Product"Backlog"Renement""
(grooming)"
In"Product"Backlog"Renement,"we"do"
some"preSplanning"for"the"upcoming"
Sprint.""I"bring"the"latest"Product"Backlog"
and"go"through"the"business"goals"with"
the"Team.""&

ATTENDEES:&
! Product"Owner"
! Team"Members"
! ScrumMaster"
&
INPUTS:&
! Latest"Product"Backlog"
TIMEBOX:"
! 10%"of""Sprint"capacity"
OUTPUT:"
! EsAmated"PBIs"
! Updated"and"ordered"Product"
Backlog&

3!
8!

Product&
Backlog&
"

New&or&
changed&PBIs&
to&es)mate&
"
28

Product"Backlog"Renement""
(grooming)"
We"help"rene"the"Product"Backlog"
by"breaking"large"PBIs"into"smaller"
items,"clarifying"and"adding"details"
and"esAmaAng"new"or"changed"
PBIs".""&

3!
8!

Product&
Backlog&
"
29

Sprint"Review"

30

Sprint"Review"

ATTENDEES:&
! The"Scrum"Team"
! Interested"Stakeholders"
INPUTS:&
! Completed"Product"Increment"
! Risks"and"issues"

The"Sprint"Review"is"a"mee)ng"
held"at"the"end"of"the"Sprint"to"
inspect&and&adapt&the&Product&as"
it"is"being"built."""

TIMEBOX:"
! Maximum"of"4"hours"for"a"one"month"
sprint"(less"if"a"shorter"Sprint"e.g."2"
hours"for"a"2"week"Sprint)"
"
OUTPUT:"
! Feedback"on"the"product"
! Clarity"and"understanding"on"the"
current"progress"and"state"of"the"
product/system."

31

Sprint"Review"
We"present&and&demonstrate&what"was"
completed"in"the"previous"Sprint"and"
solicit&feedback&for"any"changes"to"be"
made"to"the"Product"Backlog"for"the"next"
Sprint.""

Dont"spend"more"than&half&an&hour&geang&
setup"for"the"review.""Its"meant"to"be"an"
honest"review,"not"a"ashy"presentaAon.""We"
also"have"a"rule"to""show&only&things&that&are&
really&Done;"so"well"tested"and"ready"to"go."""
32

Sprint"Review"
I"add"new&or&changed&feature&ideas&to&the&
Product&Backlog&as"they"come"up"during"
the"review.""Where"there"is"a"lot"of"
feedback"from"stakeholders,"I"will"oQen"
meet"with"them"aQerwards"so"the"review"
doesnt"run"over"our"Amebox."

We"like"to"see&progress&every&Sprint.""
Its"our"chance"to"give&some&feedback"
and"ensure"we"know"whats"going"on."
We"can"nd"out"the"risks"involved"
and"catch&any&issues&early."

33

Sprint"RetrospecAve"

WHAT WENT WELL

TO IMPROVE

ISSUES TO ESCALATE

34

Sprint"RetrospecAve"
The"Sprint"RetrospecAve"is"a"
mee)ng&to&inspect&and&adapt&the&
process,"improving"the"way"the"
Scrum"Team"works,"the"techniques"
and"working"relaAonships.""

ATTENDEES:&
! The"Scrum"Team"
INPUTS:&
! Completed"Product"Increment"
! Risks"and"issues"
TIMEBOX:"
! Maximum"of"3"hours"for"a"one"month"
sprint"(less"if"a"shorter"Sprint"e.g."1.5"
hours"for"a"2"week"Sprint)"
"
OUTPUT:"
! Improvements"to"be"made"by"the"
team"
! Clarity"on"what"is"working"and"not"
working."

35

Sprint"RetrospecAve"

We"talk"about"what&went&well&during"the"
Sprint,"and"what"we"want&to&improve.""
We"decide"what"we"want"to"improve"and"
how"we"can"do"it."

"
""At"the"end,&we&pick&the&one&most&
important&thing&we"need"to"x,"and&do&it&
"

We"try"to"work"on"one"item"each"Sprint"and"
track"it"as"we"do"with"the"other"Sprint"work."""
36

Sprint"RetrospecAve"
While"many"Teams"have"their"
ScrumMaster"facilitate"the"meeAng,"
we"like"to"get"a"ScrumMaster"from"
another"Team,"or"someone"neutral"to"
facilitate"so"I"can"discuss"issues"too.""

I"also"join"the"RetrospecAve"so"
I"can"help"improve"any"issues.""
If"the"discussion"gets"into"deep"
technical"areas"then"I"can"
leave."

37

Example&
What"works"

Daily Scrum
raises blocks
early
Burndown
charts give
visibility

To"improve"

More testing
found major
bug

Estimates
need to be
more realistic

Start the Daily

Scrum on time

Need
continuous
integration

Devs involved
in user testing
labs

#1"issue"to"x"

Stop
managers
pulling devs off
the Sprint

Run one Daily

Scrum
including the
other Teams

#1 Setup
continuous
integration
38

The"key"Scrum"ArAfacts&
"

Product"Backlog"

The"Agile"version"of"a"
requirements"document.""
Made"of"Product"Backlog"
Items"(PBIs)"ordered"in"a"
way"to"deliver"high"value"and"
reduce"risk."

Sprint&Backlog"

Write
Write
serverfailing
side logic
test
Create DB
Do GUI
Write
schema
design
form
Do
validation
integratio
n test

During"the"Sprint"Planning"
meeAng"the"Team"creates"a"
set"of"tasks"they"need"to"
develop"to"deliver"the"Product"
Backlog"Items."""

"

Product"Increment"
Scrum"Teams"develop"products"
iteraAvely"and"the"results"are"
reviewed"at"the"Sprint"Review"
to"an"agreed"quality"level."
Changes"can"be"added"to"the"
Product"Backlog"to"be"worked"
on"in"a"future"Sprint."

Burndown"charts"

Sprint&Burndown&chart&
A"chart"the"Team"uses"to"track"
the"work"remaining"within"the"
Sprint."
"

Release&Burndown&
Tracks"the"whole"release"
39

I work with the Business and Team to create the

Product Backlog, an ordered list of product requests
(aka Agile requirements).
I put the most important requests at the top of
the backlog so we know what to focus on first and
can get value back faster.

The"Goal:"

increase"customer"conversion,""
have"a"great"wedding"day"

Product"
Backlog"

40

Example"Product"Backlog"
Category&
Common"
grouping"
(theme)"for"
story"

Story&(name)&
Short"descripAon"
of"the"story"

Es)mate&
ComparaAve"size"of"the"
eort,"complexity"and"risk."
In"points"or"ideal"Ame."

Notes&
Any"notes"that"will"
help"clarify"or"
quesAons"that"need"
answered."Should"
be"brief.""

#&ID&

Category&

Story&

Est&

Acceptance&tests&

Notes&

1"

Search"

As"Bobby,"I"want"to"nd"a"
CD"by"the"date"it"was"
released"so"I"can"nd"the"
recording"I"like"

5"

Search"by"month"
Search"by"day"
Search"by"year"

Can"we"accept"mulAple"
date"formats?"

2"
3"
ID&#&
Unique,"auto" 4"
generated"to"
track"against"
other"items"

Acceptance&tests&
The"condiAons"of"
saAsfacAon"from"the"
business/endSuser"
perspecAve"

41

Breaking"big"PBIs"down"
As a frequent flyer I want
to easily book a trip I
take often so that I can
save time

Change"ights"
"

As"a"frequent"yer,"I"can"
change"my"ight"iAnerary"
so"I"can"have"more"exible"
travel"plans."

As a frequent flyer I want

to request an upgrade so
that I can be more
comfortable
As a frequent flyer I
want to book a trip using
miles so that I can save
money
42

CreaAng"Acceptance"tests"for"PBIs"
Acceptance"tests"for"a"PBI"with"an"airlines"online"booking"service"for"a"
feature"request"for"a"high"status"frequent"yer.""
Change"ights"
"

As"a"frequent"yer,"I"can"
change"my"ight"iAnerary"so"I"
can"have"more"exible"travel"
plans."

Verify only premium users can access

this service
Verify flights can be changed up to 48
hours before a scheduled flight
Verify the tickets and seats are reissued correctly
Verify that an email confirmation is
sent
Verify customer service numbers
displayed if within 48 hours of a flight
43

Estimation
As a frequent
flyer I want to
book flights

?&
3!

44

EsAmaAng"
EsAmaAon"can"be"useful"for"
planning"and"budgeAng"
purposes.""It"is"done"throughout"
the"Scrum"cycles"as"new"items"
are"added"or"changed."""

Es)ma)on&should&be&done&
by&the&people&doing&the&
actual&work"i.e."the"Team"
Members."

45

EsAmaAng"
One"common"approach"is"
Planning"Poker.""The"Team"
Members"get"together"with"the"
Product"Owner"and"esAmate"the"
Product"Backlog"items."

The"Product"Owner"will"be"present"
to"provide"clarity"and"answer"
quesAons.""

46

EsAmaAng"with"Planning"Poker"
Each"Team"Member"has"a"
deck"of"special"cards.""A"
typical"deck"has"a"
1,2,3,5,8,13"or"some"
variaAon."

& 3& 5&

2
1&

8& 1
3&

Each"Team"Member"holds"
their"own"deck"so"the"
others"cant"see"them"

47

EsAmaAng"with"Planning"Poker"
The"PBI"to"be"esAmated"is"
put"on"the"table"and"I"
clarify"what"is"needed."

& 3& 5&

2
1&

8& 1
3&

We"each"then"decide"on"the"
number"we"think"the"item"
might"be"where"1"means"it"is"
simple"and"quick,"and"a"13"
means"it"is"complex"and/or"
Ame"consuming."

48

EsAmaAng"with"Planning"Poker"
We"put"the"poker"card"face"down"
on"the"table"unAl"we"are"all"
ready,"then"ip"it"over"and"look"
at"everyones"guess"

We"can"now"discuss"the"outliers;"why"some"
people"think"its"a"low"or"high"number.""We"
gain"knowledge"from"each"other"and"can"now"
reSesAmate"again"based"on"what"we"have"
learnt."

We"someAmes"go"a"few"rounds"before"agreeing"on"a"number.""
One"thing"that"can"help"is"to"agree"on"some"reference"PBIs;"
agreeing"on"the"lowest"and"highest"and"medium"items"to"
compare"the"others"against."
49

Tracking"Progress"

50

Teams&track&work&remaining&&
(not"actual"work)"during"the"
Sprint."
"
900

800

843
813
777

772
752

700

751
733
701 694
656

600

641
608
583

500
360
321

400
300

180

200

123
55

100

22

30+Mar

28+Mar

26+Mar

24+Mar

22+Mar

20+Mar

18+Mar

16+Mar

14+Mar

12+Mar

8+Mar

10+Mar

6+Mar

51

The"Scrum"Board"
Story"

In"progress"

Post!job!

Code!
!
Create!UI!
6!
!
4!

Create!UI!
!
7!

Code!
!
4!

Done!"

Code!
!
4!

The&Scrum&Board&is"a"simple"
Status"
daily"tracking"tool"to"see"
whats"in"progress."
"
900

800

843
813
777

772
752

700

751
733
701 694
656

600

641
608
583

500

Code!
!
Update!job!
Create!UI!
6!
!
4!

360
321

400

Code!
!
4!

300
180

200

123
55

100

22

30+Mar

28+Mar

26+Mar

24+Mar

22+Mar

20+Mar

18+Mar

16+Mar

14+Mar

12+Mar

Defect/
Unplanned!

8+Mar

Code!
!
Post!photo!
Create!UI!
6!
!
4!

10+Mar

Code!
!
Filter!jobs!
Create!UI!
6!
!
4!

6+Mar

Next!story!

52

900

800

843
813
777
772
752

751
733
701 694
656

700

Sprint&Burndown:"
tracks"work"remaining""

641
608
583

600

500
360
321

400
300

180

200

123
55

100

22

Tasks"

30+Mar

28+Mar

26+Mar

24+Mar

22+Mar

20+Mar

18+Mar

16+Mar

14+Mar

12+Mar

10+Mar

8+Mar

6+Mar

Mon"

Tues"

Wed"

8"

4"

8"

Code"the"middle"Aer"

16"

12"

10"

7"

Test"the"middle"Aer"

8"

16"

16"

11"

Code"the"user"interface"

Write"online"help"

12"

Thur"

Fri"

8"
53

Tracks"work"remaining"
on"release""

Release"Burndown"Chart"
Release"date"if"scope"stops"increasing"

Release"date"if"scope"keeps"increasing"

Source:!hQp://www.mountaingoatsoSware.com/alt_releaseburndown!

54

Scrum"Glossary"

55

Scrum"Glossary"1"
CrossUfuncVonal!and!selfUorganising!Team!of!2U9!
people.!

Scrum!Team!

Responsible!for!their!own!task!assignment!and!the!
how!of!delivering!the!Product.!
Determines!what!should!be!produced,!to!maximise!
return!on!investment!(ROI)!for!the!business!
Deliver!product!that!meet!the!users!needs!and!desires!

Product!Owner!
Protects!and!serves!the!Team,!and!supports!their!
pracVce!of!Scrum!
Neither!the!manager!nor!director!of!the!Team!

ScrumMaster!

Removes!impediments!the!Team!asks!them!to!
Protector,!process!master!and!problem!solver!
56

Scrum"Glossary"2"
A!VmeUboxed!iteraVon.!During!the!Sprint!no!new!
product!needs!are!added!and!the!duraVon!stays!xed.!!
Timebox:!Between!1U4!weeks!

Sprint!
The!Scrum!Team!sets!the!Sprint!Goal!and!the!
Development!Team!selects!a!porVon!of!the!Product!
Backlog.!
Timebox:!1!hr!per!week!of!Sprint!

Sprint!Planning!1!
The!Development!Team!breaks!the!Product!Backlog!
Items!into!tasks!and!work!out!how!they!will!deliver!the!
Sprint!Goal.!

Sprint!Planning!2!

!Timebox:!1!hr!per!week!of!Sprint!
57

Scrum"Glossary"3"
Sprint!!
Backlog!

The!Sprint!Backlog!is!the!task!breakdown!of!a!subset!of!
the!Product!Backlog!the!Team!creates.!
The!Team!can!add,!delete!and!update!the!tasks.!!
A!daily!meeVng!for!the!Team!to!share!what!they!have!
been!working!on,!what!they!are!about!to!work!on!and!
anything!blocking!them.!!!

Daily!Scrum!
1!
2!
3!
4!
5!
6!
7!
8!
9!
10!
11!
12!
13!

Product!
Backlog!

Timebox:!<!15!minutes.!
Agile!version!of!a!requirements!document!
Product!needs!or!Product!Backlog!Items!(BPIs)!
(requirements,!features,!defects,!documentaVon)!
ordered!into!a!list!with!highest!value!items!at!the!top!
Managed!by!the!Product!Owner!
58

Scrum"Glossary"4"
1!
2!
3!
4!
5!
6!
7!
8!
9!
10!

A!unit!of!work!small!enough!to!be!completed!by!the!Team!
in!one!Sprint.!

Product!Backlog!Items!
1!
2!
3!
4!
5!
6!
7!
8!
9!
10!
11!
12!

Product!Backlog!
Renement!

The!Product!Owner!goes!through!the!latest!Product!
Backlog!with!the!Team!and!explains!the!business!goals.!
The!Team!breaks!down!large!PBIs!into!smaller!items,!
clarifying,!adding!details,!reordering!and!esVmaVng!
new!or!changed!PBIs.!

There!are!two!types!of!tracking!charts!in!Scrum.!The!Sprint!
Burndown!which!shows!the!work!remaining!on!the!current!
Sprint,!and!the!Release!Burndown!to!show!progress!on!the!
overall!product!release.!!

Burndown!chart!
59

Scrum"Glossary"5"
Scrum!!
Board!

The!Scrum!Board!is!a!simple!tracking!tool!using!wall!space!
and!cards!to!visually!show!the!work!in!progress!during!the!
Sprint.!
The!Sprint!Review!is!the!meeVng!held!at!the!end!of!
each!Sprint!to!demonstrate!highUquality!product!
increment!built!during!the!Sprint.!It!is!open!to!all!and!
allows!for!conVnuous!feedback!from!stakeholders.!!!

Sprint!Review!

Timebox:!1!hr!per!week!of!Sprint!

Team!meeVng!to!reect!on!how!they!can!improve!
through!adjusVng!and!adapVng!their!process,!pracVces!
and!ways!of!working!together.!!!!!!

Sprint!RetrospecVve!

Timebox:!1!mth!Sprint!=!3!hrs,!2!wk!Sprint!=!1.5!hrs!
60

Scrum"Glossary"6"
Scrum!Teams!develop!products!iteraVvely!and!the!results!
or!increments!are!reviewed!at!the!Sprint!Review!to!ensure!
it!is!completed!to!an!agreed!quality!level.!

Product!Increment!

As!a!

User!Story!

R1!

R2!

R3!

Release!plan!

A!popular!way!of!wriVng!lightweight!product!requirements!
with!a!standard!form!of!As!a!<type!of!user>,!I!want!to!
<goal>!so!that!<reason>.!A!good!user!story!includes!
acceptance!criteria.!!

Plan!of!how!to!release!a!product!to!market,!may!include!
planned!release!dates.!Based!on!highest!value!items!rst.!
EsVmaVon!improves!once!team!velocity!is!stabilised!and!
known.!!!
61

Scrum"Glossary"7"
The!deniVon!of!Done!should!be!set!by!the!Team.!It!usually!
requires!PBIs!to!be!fully!tested!before!being!considered!
Done.!

Done!
1!
2!
3!
4!
5!
6!
7!
12!

Sprint!Goal!

1,3,5,8!

Sprint!Goals!are!the!PBIs!to!be!completed!by!the!end!of!
the!Sprint.!!
They!are!the!result!of!a!negoVaVon!between!the!
Product!Owner!and!the!development!team.!
Meaningful!goals!are!specic!and!measurable.!
The!Team!should!noVfy!the!Product!Owner!as!soon!as!it!
becomes!aware!it!will!not!meet!its!goals.!
RelaVve!measure!of!the!eort,!complexity!and!risk!between!
dierent!product!requests.!ComparaVve!value.!!

Story!Points!
62

Scrum"Glossary"8"
A!measure!of!how!much!capacity!and!throughput!of!work!
a!Team!can!deliver.!Can!be!thought!of!as!how!much!of!the!
Product!Backlog!a!Team!can!deliver!within!a!Sprint.!!

Velocity!
Lean'thinking!is!taken!from!the!Toyota!manufacturing!
process.!Key!principles!as!applied!to!soSware!development!
are!to!remove!waste,!improve!ow!and!amplify!learning.!!!!

Lean!

63

About&the"author"
Evolve&Beyond&&

info@evolvebeyond.com"
"
"
"

"Gabrielle"Beneeld"is"an"author,"speaker"and"advisor"specialising"in"
"Agile"and"Lean"organisaAonal"transformaAon"with"an"emphasis"on"
"product"strategy"and"innovaAon."

"
"She"is"the"founder"of"Evolve"Beyond,"a"global"consultancy"headquartered"in"London"working"
with"diverse"industries"including"nance,"telecommunicaAons,"energy"and"gaming.""
"
Gabrielle"has"used"Agile"and"Lean"methods"to"take"a"startup"to"successful"IniAal"Public"Oering,"
then"led"one"of"the"largest"Agile"enterprise"transformaAons"at"Yahoo!"scaling"up"to"250+"teams"
in"the"US,"India,"Europe,"and"Asia.""In"2009"Gabrielle"founded"the"Scrum"FoundaAon"with"Je"
Sutherland"(the"inventor"of"Scrum)"and"other"leading"Agile"thought"leaders,"to"promote"
enterprise"Agile"pracAces"within"enterprise.""
"
Gabrielle"is"an"author"of"the"Scrum"Primer"and"is"wriAng"a"book"on"Agile"and"lean"contracts"
currently."

64