Scrum is not enough v2.0

Scrum Is Not Enough v2.0
or
A few stumbling blocks that many companies
have encountered with Scrum

Ari Tanninen
Agile Saturday, Estonia, May 15th

Friday, May 14, 2010

Ari Tanninen
Software engineer, freelance agilist

Decade of product development
Telecom, on-line gaming, startups
Currently ScrumMaster & lead designer

Six years agile, three years Scrum
Five Scrum projects, coach in three


Hello, who are you?


Scrum is great!

• Individuals: clarity, pride, and joy in work
• “Move task to done, go home.”
• Companies: good projects, high quality, time
to market
• Agile is the best way to build software
(that I know of)


Scrum in a nutshell


Scrum is simple but difficult.

It’s greatest benefit is that it surfaces problems,
but Scrum is not enough to solve them.

Many companies fail with Scrum because solving
problems is difficult and change is painful.

More companies would succeed with Scrum if
they would anticipate or avoid some of the
problems.


Scrum is simple

• Minimalistic framework: demands little
• Multi-purpose
• Surfaces problems
• Catalyst for improvement and change
(if done correctly)


Scrum is difﬁcult

• Minimalistic framework: no toolbox
• Depends on change in thinking, culture,
organization structure
• Depends on trust, collaboration, teamwork
• Assumes goals, strategy, leadership


Typical problems


Broken
team


Broken team
do es
eam form
• Unclear purpose and goal T t
no

• Missing skillsets ne
• Part-time members do ing
gs ait
in w
th nd
• Distributed ingys a
tt la
ge e
n ot to d
due


Broken Missing
team teamwork


Missing teamwork
• Cross-functional team, full-time members,
clear goal, yet:
• Little collaboration pe Po
• Low energy rf
or or
ma
nc
• Unhappy team members e

• Inattention to results

Team vs. group
1. Do we trust each other?
2. Dare we communicate openly?
3. Do we understand our shared goals?
4. Are we truly dedicated to achieving these goals?
5. Can we solve our differences?
6. Is everyone participating?
7. Do we enjoy being a part of this team?


Broken Missing
team teamwork

Inadequate skills
for agile
development


Inadequate skills for
agile development
• Team working ﬁne, good energy, yet:
• Software not “done”
• Refactoring sprints Software
collapses
• Bugs
• Frustration project doomed


From Waterfall to Agile

Analysis Design Impl. Testing Deploying

February March April May June

A D I T D A D I T D A D I T D A D I T D A D


Speciﬁcation
Analysis
GUI
Architecture Design
k s !
W e
e Implementation
1 -4Testing
Integration Packaging
Deploying
Documentation Handover


Missing skills
• Automated regression testing
• Version control
• Incremental architecture, GUI design,
testing...
• Test-Driven Development, Refactoring,
Continuous Integration
• Task planning, self management, discipline

The Product
Owner role

Broken Missing
team teamwork

Inadequate skills
for agile
development


The Product Owner
role
• “How do I prioritize the Product Backlog?”
• “Figure it out!”
• No customer contact
• Unable to answer team’s questionswrong
the uilt
• Frustration At
pr
best t is b
oduc


Business model Stakeholder Scrum
v. 2.0

v. 1.0

Q2 Q3 Q4 Q1

Scheduling

Developers

Domain
Acme
Customers
Product End users


Organizational
silos
The Product
Owner role

Broken Missing
team teamwork

Inadequate skills
for agile
development


Organizational
silos
• Scrum running ﬁne, teams happy, still:
• Not much gets done Not rouvceh enal
m re
m t
• Teams lack support imp

• Turf wars between units “Scrum does
not work”


Accounting Projects IT

Product development
Acme


Organizational
silos
The Product Missing or
Owner role wrong goals

Broken Missing
team teamwork

Inadequate skills
for agile
development


Missing or
wrong goals
• “Our goal is to be agile”
• “What are we doing and why?”
• Missing success criteria
• Missing business drivers
• No buy-in No change

Failure


Managed
Product organization Business
management drivers for
in check Scrum

Good
Teamwork
team

Good agile
development skills


Done correctly Scrum helps you to succeed.

Scrum will not solve problems for you,
you need a plan for solving them.

Keep your eyes open, and good luck!


Scrum is not enough v2.0

Recommandé

Recommandé

Contenu connexe

Similaire à Scrum is not enough v2.0

Similaire à Scrum is not enough v2.0 (20)

Plus de Ari Tanninen

Plus de Ari Tanninen (11)

Dernier

Dernier (20)

Scrum is not enough v2.0