1. These presentation series are subjectedto explore the alternative yields ofAgile methods besides the well knownones; Managing Changing Priorities, better Time to Market, Higher Quality... The Scrum framework considered mostlyCopyright 2007, ACM. All rights reservedTuesday, December 18, 12

2. Alternatives to Go Agile Continuous Improvement/Kaizenby Ahmet AkdaCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 3. How often do you review yoursoftware development process?Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 4. Does a detailed software developmentprocess suits for all kinds of software projects in the company? Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 5. Traditional waymanaged projectSuccessProject closing meeting by procedure, reports...Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 6. Traditional waymanaged project Celebration, dinner,Success night out... Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 7. Traditional way managed project Stay away fromFailure project closingmeeting Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 8. Traditional waymanaged projectFailure No talking about the project in publicCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 9. Traditional waymanaged project FailureTeam splits into sides and each sideblames the others Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 10. Traditional way managed project FailureDocumentation, customer approval, testetc. processes may become more complexfor the upcoming projects Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 11. Traditional way managed project FailureDocumentation,People may customer approval, test conclude; Existingetc. processes may process should be become more complexused morefor the upcoming projects accurately Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 12. Well be using our current processes more accurately!Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 13. Actually one size doesnt t for allCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 14. Because every software product is aunique prototype and developed under the conditions of uncertainty and disagreement Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 15. Because every software product is aunique prototype and developed under the conditions of uncertainty and disagreementHuman factormakes the processbecome morecomplex, even chaotic Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 16. Agile Solution? Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 17. Kaizen (Continuous Improvement) Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 18. Process should be inspectedin at least each iteration Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 19. Improvement Areas of EciencyPeople Behaviors Quality Engineering PracticesTools being UsedCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 20. Improvement Areas of Efciency People Behaviors Quality Engineering PracticesTools being UsedCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 21. Improvement Areas of EfciencyPeople BehaviorsQuality Engineering PracticesTools being UsedCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 22. Improvement Areas of Efciency Team Behaviors QualityEngineering PracticesTools being UsedCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 23. Improvement Areas of EfciencyPeople Behaviors Quality Engineering PracticesTools being UsedCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 24. Improvement Areas of EfciencyPeople Behaviors Quality Engineering PracticesTools being Usedare inspectedCopyright 2007, ACM. All rights reservedTuesday, December 18, 12 25. Improvement points identiedcan be applied immediatelyduring the next iteration Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 26. The problems that becomevisible at the end of long periods of software development in traditionalprocesses,Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 27. Become visible more often inAgile process so that itbecomes more crucial to solve the root cause rather then thesymptom Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 28. Instead of having signicant experiences from major experiments, Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 29. Have signicant experiences from minor experiments withKaizen and iterative nature Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 30. Agile process applied with Kaizen is the universal remedy to deliver up-to-date, high quality software products Over80.000 ITprojects Standish Group Copyright 2007, ACM. All rights reservedTuesday, December 18, 12 31. www.acm-software.com@ACMSoftware@aakdagCopyright 2007, ACM. All rights reservedTuesday, December 18, 12