Alternatives to Go Agile / Transparency

586 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...

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
586
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Alternatives to Go Agile / Transparency

  1. 1. These presentation series are subjected to explore the alternative yields of Agile processes besides the well known ones; Managing Changing Priorities, better Time to Market, Higher Quality... The Scrum framework mostly considered Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  2. 2. Alternatives to Go Agile Transparency Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  3. 3. Situations of transparency... Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  4. 4. Commonality #1 - PM(Project Manager): Hi Adam, How long will ___ take, what do you think? Developer thinks: I’m very busy now and he’ll probably add more work. This one at least will take 2 days and I have a bunch of work to complete.. - Developer: About a week. PM thinks: You think so, I’ll take it as 1,5 or 2 weeks to guarantee. - PM: Thanks Adam. I’ll update the plan with this feedback. Developer thinks: Now I can delay some of these, too. Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  5. 5. Commonality #1 The costs get higher for each level as we go up in a vertically organized hierarchy PY X2 BA X2 Dev Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  6. 6. Commonality #2 Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  7. 7. Commonality #3 - Customer: Hi Alex, how is the project getting on? We have 4 months and the market is very aggressive nowadays. - PM: We’ve completed 50% as the architecture got clear! We just have coding and testing to be completed. Customer thinks: They told us the same for the previous project but it stayed at 95% for 3 months. Hopefully they’ve learned from that... - Customer: Excellent! We’ll break away if we can go live on time. - PM: We’re sure that we’re on track, don’t worry... Traceability Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  8. 8. Commonality #4 - Developer A: We just have few weeks to test ____ module. - Developer B: And we haven’t done any refactoring, we’re too slow. - Developer A: We have to speed up now, then we focus on quality. - Developer B: Good idea, otherwise we’ll not be able hit it... Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  9. 9. Commonality #4 - Developer A: We just have few weeks to test ____ module. - Developer B: And we haven’t done any refactoring, we’re behind the schedule. - Developer A: We have to speed up now, then we focus on quality. - Developer B: Good idea, otherwise we’ll not be able hit it... It’s very hard to focus on quality later as the new emergent work arrives all the time Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  10. 10. Commonality #4 Reduced quality results in increased TCO(Total Cost of Ownership) Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  11. 11. Commonality #4 Reduced quality results in increased TCO(Total Cost of Ownership) All of the stakeholders should be informed about quality Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  12. 12. Commonality #4 Reduced quality results with increased TCO(Total Cost of Ownership) All of the stakeholders should be informed about quality http://benscheirman.com/2007/10/dont-make-squirrel-burgers Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  13. 13. The probability of risk of error increases as the true information delivery and transparency decrease Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  14. 14. The probability of risk of error increases as the true information and transparency decreases Probability of Risk of Error True information/Information Transparency Ahmet Akdağ 2012 Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  15. 15. People can’t have enough time to do the job when they focus giving transparent information via expensive tools which also adds another level to complexity Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  16. 16. Agile Solution? Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  17. 17. All of the stakeholders are at the same level of knowledge with continuous delivery of working software Traceability Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  18. 18. Estimation and planning gets better as the planning is done by considering the past performance, not by considering “the most likely scenario” Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  19. 19. All of the stakeholders committed to the project has common definitions which creates a transparent ground to communicate (Definition of Done) Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  20. 20. Progress information is shared with stakeholders via frequent efficient meetings Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  21. 21. Everyone involved in the project can access easily to the project information Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  22. 22. Everyone involved in the project can access easily to the project information Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  23. 23. Stakeholders do not need to buy a tool or derange people working on the project to get information about the progress of the project Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  24. 24. Transparency is enhanced with flat hierarchy and less of roles Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  25. 25. Agile processes enhance transparency and traceability Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  26. 26. VersionOne Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  27. 27. VersionOne Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  28. 28. Agile processes that brings transparency in are the universal remedy to deliver up-to-date, high quality software products Over 80.000 IT projects Standish Group Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
  29. 29. www.acm-software.com @ACMSoftware Copyright 2007, ACM. All rights reservedMonday, January 7, 2013

×