The document discusses Agile development practices and their adoption over time. It notes that while Agile has gained popularity, not all projects using Agile see significant improvements. It questions whether success is truly related to using Agile practices, and suggests Agile addresses symptoms but not underlying causes like complexity. The document predicts the next wave in development will need to further increase productivity, effectiveness, and predictability by specializing roles and sharing expertise to reduce complexity.

1. Agile Coaches, 10 years of Agile experience We Love Agile

2. Disclaimer

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

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

7. Agile is gaining larger adoption

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

9. So how ‘wow’ are we doing?

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

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

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

14. Are success and Agile related?

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

17. Making Agile Mainstream Make it practical and concrete Training and coaching

18. What might induce the decline of Agile?

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

21. Hint: how to get out of the midlife crisis?

22. “ 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

23. Goals ‘ Wowness’ Predictability Productivity

26. Agile cures the symptomes, but leaves the causes unsolved

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

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

29. You risk spending too little effort eliciting requirements

30. Waterfall = Bad Agile = Good Assumption

31. Don’t try to pass the Agile Test

32. Don’t take the symptoms for granted

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

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

36. Manage all risks Changing requirements is not always your biggest risk

37. Effectiveness = good Non-effectiveness = bad

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

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

40. Ready for the next wave? Agile is here Next wave

41. The Agile Spirit can help us

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

44. Conclusion Measure effect , not process conformance.

45. Questions? Learn, innovate, inspire