alternatives to go agile / transparency

29
Copyright 2007, ACM. All rights reserved 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 Monday, January 7, 2013

Upload: acm

Post on 07-Nov-2014

493 views

Category:

Technology


2 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

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

Monday, January 7, 2013

Page 2: Alternatives to Go Agile / Transparency

Transparency

Copyright 2007, ACM. All rights reserved

Alternatives to Go Agile

Monday, January 7, 2013

Page 3: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Situations of transparency...

Monday, January 7, 2013

Page 4: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

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.

Monday, January 7, 2013

Page 5: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

PY

BA

Dev

X 2

X 2

The costs get higher for each level as we go up in a vertically

organized hierarchy

Commonality #1

Monday, January 7, 2013

Page 6: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Commonality #2

Monday, January 7, 2013

Page 7: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

- 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

Commonality #3

Monday, January 7, 2013

Page 8: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

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

Commonality #4

Monday, January 7, 2013

Page 9: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

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

Commonality #4

It’s very hard to focus on quality later as the new emergent work arrives all the time

Monday, January 7, 2013

Page 10: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Commonality #4

Reduced quality results in increased TCO(Total Cost of Ownership)

Monday, January 7, 2013

Page 11: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Commonality #4

All of the stakeholders should be informed about quality

Reduced quality results in increased TCO(Total Cost of Ownership)

Monday, January 7, 2013

Page 12: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

http://benscheirman.com/2007/10/dont-make-squirrel-burgers

Commonality #4

All of the stakeholders should be informed about quality

Reduced quality results with increased TCO(Total Cost of Ownership)

Monday, January 7, 2013

Page 13: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

The probability of risk of error increases as the true information delivery and

transparency decrease

Monday, January 7, 2013

Page 14: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Ahmet Akdağ 2012

Pro

babi

lity

of R

isk

of E

rror

True information/Information Transparency

The probability of risk of error increases as the true information and

transparency decreases

Monday, January 7, 2013

Page 15: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

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

Monday, January 7, 2013

Page 16: Alternatives to Go Agile / Transparency

Agile Solution?

Copyright 2007, ACM. All rights reserved

Monday, January 7, 2013

Page 17: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Traceability

All of the stakeholders are at the same level of knowledge with continuous

delivery of working software

Monday, January 7, 2013

Page 18: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Estimation and planning gets better as the planning is done by considering the

past performance, not by considering “the most likely scenario”

Monday, January 7, 2013

Page 19: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

All of the stakeholders committed to the project has common definitions which

creates a transparent ground to communicate

(Definition of Done)

Monday, January 7, 2013

Page 20: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Progress information is shared with

stakeholders via frequent efficient meetings

Monday, January 7, 2013

Page 21: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Everyone involved in the project can access easily to the project information

Monday, January 7, 2013

Page 22: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Everyone involved in the project can access easily to the project information

Monday, January 7, 2013

Page 23: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Stakeholders do not need to buy a tool

or derange people working on the project to get information about the

progress of the project

Monday, January 7, 2013

Page 24: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Transparency is enhanced with

flat hierarchy and less of roles

Monday, January 7, 2013

Page 25: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Agile processes enhance

transparency and traceability

Monday, January 7, 2013

Page 26: Alternatives to Go Agile / Transparency

VersionOne

Copyright 2007, ACM. All rights reservedMonday, January 7, 2013

Page 27: Alternatives to Go Agile / Transparency

VersionOne

Copyright 2007, ACM. All rights reservedMonday, January 7, 2013

Page 28: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

Standish Group

Agile processes that brings transparency in are the universal remedy to deliver

up-to-date, high quality software products

Over80.000

IT projects

Monday, January 7, 2013

Page 29: Alternatives to Go Agile / Transparency

Copyright 2007, ACM. All rights reserved

@ACMSoftware

www.acm-software.com

Monday, January 7, 2013