Agile: Scrum

Methodology
•Gino Paolo Villanueva, John Evangelista
•November 20, 2018

1 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agenda

1. Agile Manifesto
2. Agile VS Waterfall
3. Scrum
- Roles
- Artifacts
- Ceremonies

2 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile Manifesto

"We are uncovering better ways of

developing software by doing it and
helping others do it."

3 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile Manifesto

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

4 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile VS Waterfall

EXERCISE

5 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile VS Waterfall

Agile Waterfall
- Adaptive / Empirical - Sequential
- Predictive Approach
- Incremental Approach
Advantages:
Advantages:
1. Record keeping
1. Allows change after initial planning.
2. Has an idea of the size, cost and
2. Keeping up to date to the latest timeline for the project.
developments in the industry. Disadvantages:
3. Testing is done every sprint. 1. Cannot go back to the previous
Disadvantages step.
1. No definitive plan 2. Relies heavily on initial requirements

2. Scope creep 3. Testing is done only at the end

4. Non-flexible

6 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile VS Waterfall

7 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Agile VS Waterfall

8 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

9 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

~ Scrum is an agile process that allows us to focus on

delivering the highest business value in the shortest time.

~ It allows us to rapidly and repeatedly inspect actual

working software (every one week to one month).

~ Time-boxed and Never Extended

10 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Characteristics:
- Self-organizing, cross-functional teams
- Product progresses in a series of one- to four-week “sprints”
- Iterative feedback loops, early ROI
- Low cost of change, low risk
- Requirements are captured as items in a list of “product backlog”
- Inspect and Adapt, repeat forever

11 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

12 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

True or False:
- The most common iterations are three weeks.
- The iterations take place one after the other with pause in between.
- An improving team can use a longer cycle.

13 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Roles

•Product Owner
•ScrumMaster
•Team ≠ Scrum Team

14 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Owner
What ~What
Responsible Not
-Notthe
thesame
sameas
asaaProduct
ProductManager
-Responsibleforformaximizing
maximizingROIROI Marketing
Identifies product features Manager
Prioritize thenproduct
- Knows the re-prioritize
by heart
Knows the product by heart Not
- Notresponsible
responsiblefor
formaximizing
maximizingROI
ROI
Maintains the product backlog in in
terms ofof
terms commercial
commercial product
product
- Maintains the product backlog
Responsible for explaining to the team what is in the product backlog
Help achieve the highest business value of the product
- Responsible for explaining to the team what is in the product backlog
What
- Helpand Why the highest business value of the product
achieve

15 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Team
What ~What
Cross functional There
-There
-Not isissame
the no
nohierarchy
hierarchy ininthe
as a Producttheteam,
Marketing
team,
- Cross
-Responsible
functional
for maximizing ROI
Self managing / Self organizing everyone
everyoneisisEQUAL
Manager EQUAL
High Should not be involved in other
Selfdegree
- Knows the of
managing/ autonomy
product and
Selfbyorganizing
heart
accountability projects
--Should
Not responsible
not be involved
for maximizing
in other ROI
Multi learning Avoid changing
projects
in terms membersproduct
of commercial
- Maintains
Multi learning
the product backlog
Develops the project, composed of 7( 2) members
Create the sprint backlog
- Develops the project, composed of 7( 2) members
Provide
- Create ideas to the
the sprint Product Owner on how to make the product much better
backlog
Also known as Feature Teams
- Provide ideas to the Product Owner on how to make the product much better
How

16 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Scrum Master
What ~What
Facilitates the scrum process Does
-Doesthe
-There
-Not not
not assign
issame
no astask
assign
hierarchy
task
a Product
in theMarketing
team,
-Facilitates
-Responsible
Cross functional
thefor
scrum
maximizing
processROI
Serves the Scrum Team everyone is EQUAL
Manager
Is
-Isnot
notthe
theMANAGER!
MANAGER!
- Knows
Serves
Self managing/
the
the product
teamSelfbyorganizing
heart
Removes impediments --Should
Not responsible
not be involved
for maximizing
in other ROI
Protects
Removes from outside
impediments interference Cannot
-Cannot
projects
in termsbe the
beof
the same
sameas
commercialasPOPO
product
- Maintains
Multi learning
the product backlog
Should not be part of the Dev team
Makes sure that the team, PO and stakeholders know the principles of scrum
A coach and a teacher
- Makes sure that the team, PO and stakeholders know the principles of scrum
-Can comeand
A coach froma any background or discipline
teacher
-80
80toto90%
90%social
socialskills
skills

17 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Stakeholders
What ~What
Can be the customers, managers Cannot dictate the team
-Can be the customers, managers -Cannot dictate the team
and end users
and end users

Supports
- Supports the team
the team

Helps remove
- They make impediments
their expertise
available
They make their expertise and
experience available

18 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Artifacts

•Product backlog
•Sprint backlog
•Burndown charts

19 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Backlog

- exists (and evolves) over the lifetime of the project

- product roadmap
Good Characteristics:
1. clear and sustainable
2. fine - grained
3. well – estimated
4. emergent
5. prioritized

20 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Backlog

21 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Backlog

- output of the Sprint Planning

- list of tasks to be done by the Team in a Sprint
- work is never assigned to anybody

22 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Backlog

23 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Backlog (Scrum Board)

24 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Burndown Chart

- Used to track the progress

- Remaining estimate of work remaining against number of days

- Ideally should be a downward sloping graph

- More effective if written in a board

25 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Burndown Chart

26 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum

Ceremonies

•Definition of Done
•Sprint Planning
•Sprint Review
•Sprint Retrospective
•Daily Scrum Meeting
•Product Backlog Refinement

27 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Definition of Done
What Who
Output per iteration is potentially PO, Team, SM
-Output per iteration is potentially PO, Team, SM
shippable product
shippable product

Should
-Shouldbebe discussed beforethe
discussed before the
Sprints
Sprints start
start
Duration:
- Purposeisistotominimize
Purpose minimize delay
delayand
and Depends on
Depends onthe
theteam
team
risk
Risk
-Canbe
Can bein
in aa form
form of
of aadocument
document

28 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Planning Part 1
What Who
Preparation for sprint PO, Team, SM
- Preparation for sprint PO, Team, SM
What? and Why? by PO
- What? and Why? by PO
Create
- Createthe
theSprint
SprintGoal
Goal

Duration:
1Depends
1 hour
hour per
peron
week
the team
week ofofsprint
sprint

29 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Planning Part 2
What Who
Preparation for sprint Team, SM
- Preparation for sprint Team,
PO, Team,
SM SM
How? by Team PO
PO (optional)
(optional)
- What?
How? byandTeam
Why? by PO
Contains
- Create
Contains estimates,
theestimates, depends
Sprint Goal on
depends on
the
the team whatisisdefined
team what definednumber
number
ofofhours per day
hours per day
Forecast
-Forecastof of what canbe
what can bedone
done Duration:
(SprintCommitment)
(Sprint Commitment) 1Depends
1 hour
hour per
peron
week
the team
week ofofsprint
sprintbutbut
notnot
more
-Pokerplanning
Poker planning than 4 hours
more than 4 hours

30 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Daily Scrum / Daily Standup Meeting
What Who
Update between the members Team
- Preparation
Update
Answer for sprint
between
3 questions: the members TeamTeam,
Team,
PO, SM SM
PO
PO (optional)
(optional) , ,SM
SM(optional),
(optional),
- Answer
How?
What?
• Whatbyand
3 Team
is questions:
Why? by
DONE? PO have you
(What
- Create
Contains
•What isestimates,
the DONE? (What
Sprint Goal have you
depends on stakeholders (optional)
stakeholders (optional)
done YESTERDAY?)
the done what
team YESTERDAY?)
isDONE?
defined(What
number
• What
•Whatwill be
willday
be DONE? (What will will
of hours
you per
youdo
doTODAY?)
TODAY?)
-Forecast of
• Impediments what can be aredone Duration:
•Impediments(What
(What are the
the
(Sprint Commitment)
PROBLEMS
PROBLEMS you have
you have 15hour
1
Depends
15 minutes
peron
minutes week
the team
of sprint but not more
-Poker planning
encountered?)
encountered?) than 4 hours
- Follow
Follow upup meeting
meeting is is encouraged
encouraged
ififthere
thereare
areunclear
uncleartasks
tasks

31 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Product Backlog Refinement
What Who
Split big items, analyze, re PO, Team, other experts that can
- Preparation
Split big items,
prioritize, for analyze,
sprint re SM other
TeamTeam,
Team,
PO, SM experts that can help
help
PO (optional) , SM (optional),
-prioritize,
How? by
What? and Team
Why? by PO
It- is
Contains
Create
not fortheestimates,
theSprint
items Goaldepends on
currently stakeholders (optional)
-It isteam
the
handled notbyfor
what
theteam
the isitems
defined
currently
number
handled
of hours byperthe
dayteam
-Forecast
Time of whatofcan
for analysis be done
future PB Duration:
-Time
(Sprint
items for
Commitment)
analysis of future PB 10%
15
1
Depends
10%hour
minutes
ofper
of the
on
the week
capacity
the team
of sprint
capacity ofofthebut
team
the notfor
team more
items
-Poker planning that sprint
than 4 hours
for that sprint

32 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Review
What Who
Coined to a “demo” but not really PO, Team, SM
- Preparation
Coined
Split bigtoitems,for analyze,
a “demo” sprintbut not
re really Team,
PO, SM other
TeamTeam, SM experts that can help
Stakeholders
Stakeholders
PO , (optional)
(optional) (optional)
SM (optional),
-prioritize,
No How?
What? by
andTeamWhy? by PO
ppt presentations!!
--No
Contains
Create
ppt presentations!!
theestimates,
Sprint Goal depends on stakeholders (optional)
End-It isteam
the not for
users what
willtheisitems
use defined
currently
number
the system not
-
handled
ofEnd
hours
the team users
by
per the
will
dayteam
use the system not
the team of what can be done
-Forecast Duration:
-Time for
(Sprint
Inspect Commitment)
andanalysis of futurelevel)
adapt (product PB 1Depends
10%
15
1 hour
minutes
hourofper
the
peronweek
capacity
the team
week ofofsprint
of thebut
sprint team
notfor
more
items
-Inspectplanning
-Poker and adapt (product level) that sprint
than 4 hours

33 © Nokia Solutions and Networks 2014

<Change information classification in footer>
Scrum
Sprint Retrospective
What Who
Inspect and Adapt (Process and Team, SM
Preparation
--Inspect
Coined
Split
Environment bigand
toitems,for analyze,
alevel)
Adapt sprint
“demo” (Process
but not
re really
and SM other
TeamTeam,
Team,
PO, SM experts that can help
PO (optional),
Stakeholders
PO (optional)
(optional),(optional)
,Stakeholders
SM (optional),(optional)
Environment
-prioritize,
How? by
What? and Team
Why?
level) by PO
--No
Contains
Create
ppt presentations!!
theestimates,
Sprint Stakeholders (optional)
stakeholders (optional)
What is working and Goal
depends
what’s not on
-What
-It
the isteam
not
is for
working
what theisitems
defined
and what’s
currently
number
not
- End
handled
of hoursusers
by
perthewill
dayteam
use the system not
the team of what can be done
-Forecast Duration:
-Time forCommitment)
(Sprint analysis of future PB 45hour
10%
15
1
Depends
45 minutes
ofper
the
minutes onweek
capacity
per
theweek
per team
of sprint
weekofofthe
ofsprint
but
team
notfor
sprint more
items
-Inspectplanning
-Poker and adapt (product level) that sprint
than 4 hours

34 © Nokia Solutions and Networks 2014

<Change information classification in footer>
 Questions?

35 © Nokia Solutions and Networks 2014

<Change information classification in footer>