Your SlideShare is downloading. ×
Alternatives to Go Agile / Kaizen
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Alternatives to Go Agile / Kaizen

509
views

Published on

These presentation series are subjected to explore the alternative yields of Agile methods besides the well known ones; Managing Changing Priorities, better Time to Market, Higher Quality...

These presentation series are subjected to explore the alternative yields of Agile methods besides the well known ones; Managing Changing Priorities, better Time to Market, Higher Quality...


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
509
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. These presentation series are subjected to explore the alternative yields of Agile methods besides the well known ones; Managing Changing Priorities, better Time to Market, Higher Quality... The Scrum framework considered mostly Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 2. Alternatives to Go Agile Continuous Improvement/Kaizen by Ahmet Akdağ Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 3. How often do you review your software development process? Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 4. Does a detailed software development process suits for all kinds of software projects in the company? Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 5. Traditional way managed project Success Project closing meeting by procedure, reports... Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 6. Traditional way managed project Celebration, dinner, Success night out... Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 7. Traditional way managed project Stay away from Failure project closing meeting Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 8. Traditional way managed project Failure No talking about the project in public Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 9. Traditional way managed project Failure Team splits into sides and each side blames the others Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 10. Traditional way managed project Failure Documentation, customer approval, test etc. processes may become more complex for the upcoming projects Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 11. Traditional way managed project Failure Documentation, People may customer approval, test conclude; ‘Existing etc. processes may process should be become more complex used more for the upcoming projects accurately’ Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 12. We’ll be using our current processes more accurately! Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 13. Actually one size doesn’t fit for all Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 14. Because every software product is a unique 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 a unique prototype and developed under the conditions of uncertainty and disagreement Human factor makes the process become more complex, 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 inspected in at least each iteration Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 19. Improvement Areas of Efficiency People Behaviors Quality Engineering Practices Tools being Used Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 20. Improvement Areas of Efficiency People Behaviors Quality Engineering Practices Tools being Used Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 21. Improvement Areas of Efficiency People Behaviors Quality Engineering Practices Tools being Used Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 22. Improvement Areas of Efficiency Team Behaviors Quality Engineering Practices Tools being Used Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 23. Improvement Areas of Efficiency People Behaviors Quality Engineering Practices Tools being Used Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 24. Improvement Areas of Efficiency People Behaviors Quality Engineering Practices Tools being Used are inspected Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 25. Improvement points identified can be applied immediately during the next iteration Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 26. The problems that become visible at the end of long periods of software development in traditional processes, Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 27. Become visible more often in Agile process so that it becomes more crucial to solve the root cause rather then the symptom Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 28. Instead of having significant experiences from major experiments, Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 29. Have significant experiences from minor experiments with Kaizen 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 Over 80.000 IT projects Standish Group Copyright 2007, ACM. All rights reservedTuesday, December 18, 12
  • 31. www.acm-software.com @ACMSoftware @aakdag Copyright 2007, ACM. All rights reservedTuesday, December 18, 12