The state of agile in ten easy learned lessons

@aahoogendoorn
The state of agile in ten easy lessons learned
Sander Hoogendoorn
Author of This Is Agile
@aahoogendoorn
BEYOND BREAKING BAD

BEYOND BREAKING BAD. THE STATE OF AGILE IN TEN EASY LESSONS ©2001 -2014 Sander Hoogendoorn. All Rights Reserved
@aahoogendoorn
2
Sander Hoogendoorn
Me independent.. (February 2015)
Dad
Mentor, trainer, software architect, programmer
Books, articles, conferences
Work
Principal technology officer Capgemini
Global design authority agile Capgemini
Chief technology officer insurance company
Web
www.sanderhoogendoorn.com
www.smartusecase.com
www.speedbird9.com
@aahoogendoorn
sander@ditisagile.nl

@aahoogendoorn

@aahoogendoorn
4
Introducing the Netherlands. December 5!
Name: Sinterklaas
Born: December 5
Age: 700+
Name:
Black Pete
Colour:
Not really black
(yes it’s make up)

@aahoogendoorn
Why it fails
THE WATERFALL MODEL

@aahoogendoorn
6
Waterfall?

@aahoogendoorn
11
We’ve got a plan and we’ll stick to it

@aahoogendoorn
12
Boehm’s Law. Testing is always too late

@aahoogendoorn
14
Waterfall?

@aahoogendoorn
Lesson one
AGILE IS NOT YOUR SILVER BULLET

@aahoogendoorn
16
Trying something different

@aahoogendoorn
17
The state of agile

@aahoogendoorn
18
Agile is dead

@aahoogendoorn
19
Agile conferences…

@aahoogendoorn
20
Manifesto for what again?

@aahoogendoorn
Lesson two
HAVING SOME PROCESSIS NOT A BAD THING

@aahoogendoorn
24
We are uncovering better ways to change the world?

@aahoogendoorn
25
Process? What process?

@aahoogendoorn
26
What do you mean Scrum is not a process?

@aahoogendoorn 28

@aahoogendoorn
29
FDD. Adding some process

@aahoogendoorn
30
Smart. Adding some processCreateproject proposalWriteproject planDeliverworkingsoftwareStabilizesoftware

@aahoogendoorn
31
DSDM. Adding more process

@aahoogendoorn
33
Boehm’s Law applied to iterations

@aahoogendoorn
Lesson three
THE SCRUM MASTER ISN’T ALWAYS A MASTER
?

@aahoogendoorn
37
Lowering our fences

@aahoogendoorn
38
Lowering our fences

@aahoogendoorn
39
Dogmagile

@aahoogendoorn
40
Become a scrum master? A servant-leader-master?

@aahoogendoorn
41
Scrumman

@aahoogendoorn
42

@aahoogendoorn
Lesson four
LOOSE THE SCRUM BOARD

@aahoogendoorn
WHAT’S THE REAL STATUS?

@aahoogendoorn
VISUALIZE YOUR FLOW…

@aahoogendoorn
…AND GO WITH THE FLOW

@aahoogendoorn
Not exactly like Kanban? Who cares. It works for us
LIMIT WIP?

@aahoogendoorn
49
Boehm’s Law applied to backlog items

@aahoogendoorn
50
Do we really need projects?

@aahoogendoorn
Lesson five
WE ARE NOT MANUFACTURING

@aahoogendoorn
How long do you need to build this feature?
Eh .. I don’t know. It depends I guess
20 hours.

@aahoogendoorn
Please for once give me an exact number you silly nerd!
Stop asking me these things I don’t really have an answer to

@aahoogendoorn
55
We are using the wrong metaphors
How long do you need to build this feature?
buildthis

@aahoogendoorn
56
Manufacturing? Construction?
Manufacturing and construction are linear processes
Software development is a creative process and it is very much non-linear
Software isn’t Built, it’s Invented
Coding is a creative problem. Every time a developer writes code, he is taking a non-deterministic path towards an unknown solution — a unique solution that has never been created before. If the work weren’t unique, he wouldn’t need to write it, he’d simply copy and paste it.

@aahoogendoorn
Lesson six
SELF-ORGANIZATIONCANBEPRETTYTOUGH

@aahoogendoorn
61
Magic!

@aahoogendoorn
62
Drawing owls

@aahoogendoorn
Lesson seven
ALLOW THE TEAM TO LEARN

@aahoogendoorn
GERALD WEINBERG

@aahoogendoorn
67
Learning how to play pinball

@aahoogendoorn
68

@aahoogendoorn
69

@aahoogendoorn
70

@aahoogendoorn
“Whenever I suggest stepping back, easing up, laughing a little at ourselves, and going outside our own field, somebody objects, saying, ‘But software is different. We have to work harder, concentrate more, because nothing is as complex as software.’
Well, of course software is different, and more complex than anything people have ever before attempted to engineer. But that’s why we have to loosen our structures, not tighten them. That’s why we must learn from any place we can, any way we can.”
–Gerald Weinberg, 1982.

@aahoogendoorn
Lesson eight
TRUST THE METRICS

@aahoogendoorn
74
With creative work estimates are rarely linear

@aahoogendoorn
So no projects? No estimates?
LEARN TO LIVE WITH AMBIGUITY

@aahoogendoorn
How big is this feature?
Eh .. I don’t know. It depends I guess
About 4 points.

@aahoogendoorn
77
Those who do the work, do the estimate

@aahoogendoorn
Lesson nine
YOU ARE NOT USAINBOLT

@aahoogendoorn
79
Sprints. Scrum’s mini-projects
The team commits
to deliver

@aahoogendoorn
81
The red sprint anti-pattern

@aahoogendoorn
83
Reverse planning

@aahoogendoorn
84
Trust the metrics

@aahoogendoorn
Lesson ten
PROJECT MANAGERS ARE (NOT) A TOTAL WASTE AFTER ALL

@aahoogendoorn
Instructing the team how to march
THE TRADITIONAL PROJECT MANAGER

@aahoogendoorn
90
The traditional project manager
ProjectManager
Customer
Analyst
UI Designer
Architect
Developer
Developer
Tester

@aahoogendoorn
“AGILE” PROJECT MANAGERS FACILITATE THE TEAM

@aahoogendoorn
93
The agile team facilitator
Team
Customer
Analyst
UI Designer
Developer
Developer
Tester
ProjectManager

@aahoogendoorn
MANAGE THE ENVIRONMENT

@aahoogendoorn
97
Isn’t that what the scrum master does?

@aahoogendoorn
99
This is where a project manager comes in handy

@aahoogendoorn
IN RETROSPECTIVE?

@aahoogendoorn
101
In theory…
•The whole organization is already working agile
•You don’t need a steering committee
•Budget flows automatically
•Everybody wants to collaborate
•Teams are self-steering
•You don’t need a process
•No external parties are involved
•The product owner perfectly represents all stakeholders
•No project manager is needed
•The Scrum Master is our hero
•You always make the sprint
But in practice
You’re likely the first agile project in the organization
Management requires a steering committee
Budgets need to be guarded
People are conservative
Self-steering is hard
A little process is unavoidable
There are always external parties
The product owner only represents a sub-set of all stakeholders
Yes they are needed!
The Scrum Master is too junior
Sprints “fail” all the time

@aahoogendoorn
Lesson ten
THERE IS NO SO THING AS ONE-SIZE-FITS-ALL AGILE

@aahoogendoorn
103
Agile is a sliding scale
Ceremony
Agility

@aahoogendoorn
THERE’S VALUE FOUND IN ALL AGILE APPROACHES. AND EVEN IN WATERFALL

@aahoogendoorn
Available from amazon.com
THIS IS AGILE

@aahoogendoorn
www.sanderhoogendoorn.comwww.smartusecase.comwww.speedbird9.com
sander@ditisagile.nl
@aahoogendoorn
REFERENCES AND QUESTIONS

The state of agile in ten easy learned lessons

Recommended

Recommended

More Related Content

Similar to The state of agile in ten easy learned lessons

Similar to The state of agile in ten easy learned lessons (14)

More from Sander Hoogendoorn

More from Sander Hoogendoorn (20)

Recently uploaded

Recently uploaded (20)

The state of agile in ten easy learned lessons