Scrum in 5 Minutes

&
10 Pitfalls
Staffan Persson
May 13th 2014
www-softhouse.se
2


Speech



Q & A
Name Staffan Persson
Age 47
Experience 24 years i Software Business
ABB, Axis, Ericsson, IKEA, Ikano
IBM/Rational, Sony m.fl.
Skills Agil coach, Educator,
Project Manager, Scrum Master,
Product Owner, Business Analyst
Contact staffan.persson@softhouse.se
Who am I?
3
3 Things
4
... we wish were true
The customer knows what he wants
The developers know how to build it
Nothing will change along the way

... we have to live with
The customer discovers what he wants
The developers discover how to build it
Many things change along the way
Scrum in 5 minutes
Scrum
Change!
7
8
Scrum ...
Ground Pillars
9
Inspect
&
Adapt
Prioritized
Product
Backlog
Time-boxed,
incremental
delivery
Cross-functional,
Self-organizing
teams
10
Scrum Lifecycle
Roles
Product Owner
- Stakeholders
Artefacts
Meetings
Product Owner
What? Why? When?

Stakeholder Management

Product Vision and Goal

ROI and Release Planning

Product Acceptance

Prioritized Product Backlog
11
Im not a project
manager
12
Scrum Lifecycle
Roles
Product Owner
- Stakeholders
Team
Artefacts
Meetings
Team
13
How? Who? When?

5 9 individuals

Product Increments

Product Quality

Self-organizing, Cross-functional

Committed, succeeds & fails together
We dont have any
specific roles, but
work full time in
the team and sit
together
14
Scrum Lifecycle
Roles
Product Owner
- Stakeholders
Team
Scrum Master
Artefacts
Meetings
15
Scrum Master
Coach Team & Product Owner

Encourage, support, facilitate

Remove obstacles

Shield the team

Follow the rules

Im not the tech guru,
but sometimes part
of the Team
16
Scrum Lifecycle
Artefacts
Product Backlog
Meetings
Roles
Product Owner
- Stakeholders
Team
Scrum Master
Product Backlog
17
One wish list

Owned by the Product Owner

Maintained and posted visibly

Derived from Business Plan or Product Vision
18
Scrum Lifecycle
Artefacts
Product Backlog

Meetings
Sprint Planning
Roles
Product Owner
- Stakeholders
Team
Scrum Master
Sprint Planning
19
Participants:
Set Sprint Goal
Select Product Backlog items
Create Sprint Backlog
Goal:
Agenda:
Present Product Vision (Product Owner)
Select Product Backlog items
Define Sprint Goal
Create Sprint Backlog (Team)
Mutual commitment
Product
Owner
Scrum
Master
Team
20
Scrum Lifecycle
Artefacts
Product Backlog
Sprint Backlog
Meetings
Sprint Planning
Roles
Product Owner
- Stakeholders
Team
Scrum Master
Sprint Backlog
21
22
Scrum Lifecycle
Artefacts
Product Backlog
Sprint Backlog
- Sprint Burndown
- Impediment List

Meetings
Sprint Planning
Daily Scrum
Roles
Product Owner
- Stakeholders
Team
Scrum Master
Daily Scrum
23
Purpose: Synchronize Team - work and progress
Create visibility
Scrum Master Product Owner
Im just
listening!
1. Since last meeting I did ...
2. Until next meeting I will ...
3. This is in my way ...
Some task

12
_______
_______
_______
Lets focus
on 3 Qs
Impediments
Im ashamed
of being late
Started
Some task

6
Not Started Done
John 8 /
Team
Some task

6 John 0 /
Some task

3
Team Room Booked
Every day
09.00 09.15
Some task

12
Some task

6 John
Daily Scrum
24
Purpose: Synchronize teams work and progress
Create visibility
Scrum Master Product Owner
Im just
listening!
_______
_______
_______
Sprint Burndown
Lets check that
were on track
Started Not Started Done
John 8 / 0 /
Some task

3
Team Room Booked
Every day
09.00 09.15
Team
Impediments
25
Burndown Warning Signals
E
T
C

(
h
o
u
r
s
)

Day in Sprint
Day in Sprint
E
T
C

(
h
o
u
r
s
)

26
Scrum Lifecycle
Artefacts
Product Backlog
Sprint Backlog
- Sprint Burndown
- Impediment List
Product Increment
Meetings
Sprint Planning
Daily Scrum
Roles
Product Owner
- Stakeholders
Team
Scrum Master
27
Scrum Lifecycle
Artefacts
Product Backlog
Sprint Backlog
- Sprint Burndown
- Impediment List
Product Increment
Meetings
Sprint Planning
Daily Scrum
Sprint Review
Roles
Product Owner
- Stakeholders
Team
Scrum Master
Sprint Demo
Sprint Retrospective
29
Participants:
Give opportunity for Team reflection
Improve by learning from past experiences
Reach Team commitment on prio and next
action
Goal:
Agenda:
Answer four questions:
what worked well (keep doing)?
what shall we stop doing?
what shall we start doing?
what still puzzles us?
Establish action plan
Scrum
Master
Team
What are We Building?
33
1. The product shall have a gasoline engine

2. The product shall have four wheels
2.1 The product shall have a rubber tire mounted to each wheel

3. The product shall have a steering wheel

4. The product shall have a carbon fibre body

5. The product shall be red

6. As a driver in the Ferrari F1-team, I want to drive a car that is
faster and more reliable than our competitors, so that our
team will win the title in 2014.
10 Pitfalls
# 10 Too Little Documentation
Agile & Lean means only writing the documentation we really
need








May lead to:
Strong dependencies on individuals
Need to read the code
Higher risk

# 9 Part Time Resources
Self-organization builds on dedicated teams working tightly
together with team members really trusting each other








May lead to:
Weak teams
Task switching
Low throughput of done projects
# 8 Someone Else Decides
A self-organizing team decides by them self how to solve
problems they have








May lead to:
Low motivation
Less co-operation and innovation
Unsure plans
# 7 No Continuous Improvement
Agile build on Inspect and Adapt and an evolving process.









May lead to:
Full potential not reached
Expensive to iterate
Falling back to old ways of working

# 6 Not enough co-operation
Scrum and Agile builds on close co-operation. Some
documentation is replaced by discussions and co-operation








May lead to:
Weak teams
Strong dependencies on individuals
Less innovation
# 5 Scrum without Understanding
The parts of Scrum builds a well functioning whole based on Agile
values








May lead to:
The other pitfalls
Crappy process
# 4 Scrum is a Silver Bullet
Scrum is a simple, but effective, framework to support iterative
work in self-organising teams under continuous improvement.








May lead to:
Desired effect not given
Underestimate the change
Choose the wrong tools

# 3 Wrong Team Set-up
Scrum means cross-functional, self-organizing teams building a
product in increments








May lead to:
Interdependent teams
Less innovation
Less commitment
# 2 Waterfall with Scrum
Scrum has no phases. Requirements and the product evolve
continuously while we learn








May lead to:
Not being agile Not always working with highest value
Unnecessary features
Insecure plans
# 1 Wrong Product Owner
A good Product Owner has
- a clear Vision
- a clear view of priorities,
- a budget
- time for the teams




May lead to:
Wrong product
Right product but wrong features
Ineffective development with low motivation
Conclusion
Scrum is a very powerful framework that can make large
improvement.

But, its harder than you think and there are a lot of pitfalls.

Thank You
See You!