Agile's Future Wave

Agile Coaches, 10 years of Agile experience We Love Agile

Disclaimer

Our presentation will take about 60 minutes, Please note your questions for after the presentation.

Agile status
Agile’s life cycle
The next wave?
Agile assumptions
Our prediction

Our definition of Agile
Values
Principles
Practices
“ I ndividuals over processes” “ Deliver frequently ” U nit tests Pair programming Integrate often Scrum XP

“ We are uncovering better ways of developing software by doing it and helping others do it. ” - agilemanifesto.org -

Agile is gaining larger adoption

We’re doing Agile But what was the original goal? “ Wow effect!”

So how ‘wow’ are we doing?

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

Do you know how much you have improved due to Agile?

So what does Agile solve? What does it leave unsolved?

Agile is like a red convertible It’s cool, but does it always get you what you need? Perhaps not…

Are success and Agile related?

Agile status
The next wave?
Agile assumptions
Our prediction

Agile’s Life Cycle Agile is here Rogers' bell curve

Making Agile Mainstream Make it practical and concrete Training and coaching

What might induce the decline of Agile?

Agile status
The next wave?
Agile assumptions
Our prediction

What does the next wave need to bring to overtake Agile?

Hint: how to get out of the midlife crisis?

“ Increase productivity through more efficient use of labor and more effective value propositions for customers” “ In recent years, software development productivity has stagnated” Poppendiecks on productivity

Goals ‘ Wowness’ Predictability Productivity

Agile status
The next wave?
Agile assumptions
Our prediction

Agile Assumptions
Software development = complex
Requirements change Agile = good, waterfall = bad

Agile cures the symptomes, but leaves the causes unsolved

Software development = complex What have we done to reduce complexity? symptom

If you assume requirements will change, even unchanged requirements will surprise you. Requirements change symptom

You risk spending too little effort eliciting requirements

Waterfall = Bad Agile = Good Assumption

Don’t try to pass the Agile Test

Don’t take the symptoms for granted

Agile status
The next wave?
Agile assumptions
Our prediction

Agile solves some of the problems But naturally, it leaves some too

Suppose you can’t use Agile? How will you be effective?

Manage all risks Changing requirements is not always your biggest risk

Effectiveness = good Non-effectiveness = bad

Specialization is essential for increased productivity Knowledge sharing and expert coordination to reduce complexity

Agile (XP) promotes generalists Only family physicians but no specialists?

Ready for the next wave? Agile is here Next wave

The Agile Spirit can help us

“ We are uncovering better ways of developing software by doing it and helping others do it. ” - agilemanifesto.org -

Agile status
The next wave?
Agile assumptions
Our prediction

Conclusion Measure effect , not process conformance.

Questions? Learn, innovate, inspire

Agile's Future Wave

by machielg on Aug 26, 2008

Accessibility

Categories

Tags

Upload Details

Usage Rights

Statistics

Agile’s Future Wave — Presentation Transcript