• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Alternatives to Go Agile / Transparency
 

Alternatives to Go Agile / Transparency

on

  • 429 views

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

Statistics

Views

Total Views
429
Views on SlideShare
429
Embed Views
0

Actions

Likes
0
Downloads
3
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Alternatives to Go Agile / Transparency Alternatives to Go Agile / Transparency Presentation Transcript

    • 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
    • Alternatives to Go Agile Transparency Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • Situations of transparency... Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • 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
    • 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
    • Commonality #2 Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • 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
    • 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
    • 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
    • Commonality #4 Reduced quality results in increased TCO(Total Cost of Ownership) Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • 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
    • 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
    • The probability of risk of error increases as the true information delivery and transparency decrease Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • 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
    • 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
    • Agile Solution? Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • 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
    • 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
    • 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
    • Progress information is shared with stakeholders via frequent efficient meetings Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • Everyone involved in the project can access easily to the project information Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • Everyone involved in the project can access easily to the project information Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • 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
    • Transparency is enhanced with flat hierarchy and less of roles Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • Agile processes enhance transparency and traceability Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • VersionOne Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • VersionOne Copyright 2007, ACM. All rights reservedMonday, January 7, 2013
    • 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
    • www.acm-software.com @ACMSoftware Copyright 2007, ACM. All rights reservedMonday, January 7, 2013