agile's future wave
DESCRIPTION
Improvement of Software Development should focus on what is effective, not conformance to principlesTRANSCRIPT
Agile Coaches, 10 years of Agile experience
Agile Coaches, 10 years of Agile experience
We Love AgileWe Love Agile
Disclaimer
Disclaimer
Our presentation will take about 60 minutes, Please note your questions for after the presentation.
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile
assumptions5.Our prediction
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile
assumptions5.Our prediction
Our definition of Agile
Our definition of Agile
1.Values2.Princip
les3.Practic
es
1.Values2.Princip
les3.Practic
es
“Individuals over processes”
“Individuals over processes”“Deliver
frequently”
“Deliver frequently”
Unit testsUnit tests
Pair programmingPair programming
Integrate oftenIntegrate often
ScrumScrum
XPXP
“We are uncovering better ways of developing software by
doing it and helping others do it.”
- agilemanifesto.org -
“We are uncovering better ways of developing software by
doing it and helping others do it.”
- agilemanifesto.org -
Agile is gaining larger adoption
Agile is gaining larger adoption
We’re doing AgileBut what was the original goal?
We’re doing AgileBut what was the original goal?
“Wow effect!”
“Wow effect!”
So how ‘wow’ are we doing?So how ‘wow’ are we doing?
50% of ICT projects are not successful Dutch ict-research
(ictbarometer.nl)
50% of ICT projects are not successful Dutch ict-research
(ictbarometer.nl)
Only 30% of the projects using Agile see a big improvement - Agile Adoption Survey 2008
Only 30% of the projects using Agile see a big improvement - Agile Adoption Survey 2008
Do you know how much you have improved due
to Agile?
Do you know how much you have improved due
to Agile?
So what does Agile solve?
What does it leave unsolved?
What does it leave unsolved?
Agile is like a red convertible
Agile is like a red convertible
It’s cool, but does it always get you what you need? Perhaps
not…
It’s cool, but does it always get you what you need? Perhaps
not…
Are success and Agile related?
Are success and Agile related?
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile
assumptions5.Our prediction
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile
assumptions5.Our prediction
Agile’s Life Cycle
Agile’s Life Cycle
Rogers' bell curve
Agile is here
Agile is here
Making Agile Mainstream
Making Agile Mainstream
Make it practical and concrete
Make it practical and concrete
Training and coachingTraining and coaching
What might induce the decline of Agile?
What might induce the decline of Agile?
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile
assumptions5.Our prediction
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile
assumptions5.Our prediction
What does the next wave need to bring to
overtake Agile?
What does the next wave need to bring to
overtake Agile?
Hint: how to get out of the
midlife crisis?
Hint: how to get out of the
midlife crisis?
“Increase productivity through more efficient use of labor and more
effective value propositions for
customers”
“Increase productivity through more efficient use of labor and more
effective value propositions for
customers”
“In recent years, software development productivity has
stagnated”
“In recent years, software development productivity has
stagnated”
Poppendiecks on productivity
Poppendiecks on productivity
GoalsGoals
‘Wowness’
‘Wowness’
Predictability
Predictability
Productivity
Productivity
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile assumptions5.Our prediction
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile assumptions5.Our prediction
Agile AssumptionsAgile Assumptions
Software development = complexSoftware development = complex
Requirements change
Requirements change
Agile = good, waterfall = badAgile = good, waterfall = bad
Agile cures the symptomes, but leaves the causes unsolved
Agile cures the symptomes, but leaves the causes unsolved
Software development = complex
Software development = complex
What have we done to reduce complexity?
What have we done to reduce complexity?
symptomsymptom
If you assume requirements will
change, even unchanged requirements will surprise you.
If you assume requirements will
change, even unchanged requirements will surprise you.
Requirements change
Requirements change
symptomsymptom
You risk spending too little effort eliciting
requirements
You risk spending too little effort eliciting
requirements
Waterfall = Bad
Waterfall = Bad
Agile = Good
Agile = Good
Assumption
Assumption
Don’t try to pass the Agile
Test
Don’t try to pass the Agile
Test
Don’t take the symptoms for
granted
Don’t take the symptoms for
granted
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile assumptions5.Our prediction
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile assumptions5.Our prediction
Agile solves some of the problems
Agile solves some of the problems
But naturally, it leaves some too
But naturally, it leaves some too
Suppose you can’t use Agile?
Suppose you can’t use Agile?
How will you be
effective?
How will you be
effective?
Manage all risks
Manage all risks
Changing requirements is not always your biggest
risk
Changing requirements is not always your biggest
risk
Effectiveness = good
Effectiveness = good
Non-effectiveness = bad
Non-effectiveness = bad
Specialization is essential for increased
productivity
Specialization is essential for increased
productivity
Knowledge sharing and expert
coordination to reduce
complexity
Knowledge sharing and expert
coordination to reduce
complexity
Agile (XP) promotes generalists
Agile (XP) promotes generalists
Only family physicians but no specialists?
Only family physicians but no specialists?
Ready for the next wave?
Agile is here
Agile is here
Next waveNext wave
The Agile Spirit can help us
The Agile Spirit can help us
“We are uncovering better ways of developing software by
doing it and helping others do it.”
- agilemanifesto.org -
“We are uncovering better ways of developing software by
doing it and helping others do it.”
- agilemanifesto.org -
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile assumptions5.Our prediction
1.Agile status2.Agile’s life
cycle3.The next wave?4.Agile assumptions5.Our prediction
ConclusionConclusion
Measure effect, not process conformance.
Measure effect, not process conformance.
Questions?Questions?
Learn, innovate, inspire
Learn, innovate, inspire