Ten Pitfalls in the Agile Journey

Post on 31-May-2015

229 views 0 download

Tags:

description

Agile is fast becoming one of the most widely adopted methodologies for software delivery. We have seen many organisations go through these journeys and change over the past few years. Some we have been a part of and some not. Some of our observations has been that as with any other change initiative, Agile Transformation goes into a lull after the initial euphoria has worn out. What are some of the pitfall of this journey and how can one look at avoiding them is what this talk focuses on.

Transcript of Ten Pitfalls in the Agile Journey

Ten pitfallson theAgile Journey

Gabriel GavassoProject Manager and Business AnalystASEAN expansion ggavasso@thoughtworks.com

Mar 2014

Created in collaboration with Preethi Madhu and Umar Akhter.

This presentation is licensed under Creative Commons CC BY-SA 4.0.

Gabriel Gavasso9+ formally employed in ITProject Manager, Business Analyst, Trainer, CoachWorked in Brazil, USA and Singapore

overloaded release cycles

1

New requirement

comes in something

should go out1

certifcations are ALL you need to

change the game

2

Practice and experience

across various projects.

Failing and learning. 2

Engineering Practices are not for me

3

Engineering Practices are not for me

3Have a holistic approach

across process &

engineering

anything can change anytime4

Process of negotiation

is involved for change.4

Agile means nodocumentation

5

Doc when needed and

to the extent needed.

Living docs helps! 5

empowered teams means indiscipline

6

Teams still require

guidance and support,

sometimes oversight

6

never know when it will be over7

Adaptive Planning

7

8you Scrum so you're Agile

There is no “one size

fts all” here. What is

your own favor? 8

Agile means micromanagement

9

The earlier to know, the

cheaper and the better

chances to fx are9

always strechedon projects

10

always strechedon projects

Sustainable pace and

self-organizing teams

10

New requirement

comes in something

should go out too

New requirement

comes in something

should go out

New requirement

comes in something

should go out too

Practice and experience

across various projects.

Failing and learning.

New requirement

comes in something

should go out too

Have a holistic approach across

process & engineering

New requirement

comes in something

should go out tooProcess of negotiation

is involved for change.

New requirement

comes in something

should go out too

Doc when needed and

to the extent needed.

Living docs helps!

1

32

45

New requirement

comes in something

should go out too

Teams still require

guidance and support,

sometimes oversight

New requirement

comes in something

should go out tooAdaptive Planning

New requirement

comes in something

should go out too

There is no “one size

fts all” here. What is

your own favor?

New requirement

comes in something

should go out too

The earlier to know, the

cheaper and the better

chances to fx are

New requirement

comes in something

should go out tooSustainable pace and

self-organizing teams

6

87

901

26

Thank you!Questions? Comments?

(all pictures are license-free or licensed on Creative Commons at time of use – March 24th, 2014)[1] http://www.fickr.com/photos/tokyogoat/2936378536[2] http://www.fickr.com/photos/irvotheturbo/3973939419[4] http://good-wallpapers.com/misc/12188[5] http://www.fickr.com/photos/dfucs/2715460622[6] http://www.fickr.com/photos/anthonybaker/196630774[7] http://www.fickr.com/photos/racecarphotos/535337722[8] http://www.fickr.com/photos/royskeane/413103429[9] http://www.fickr.com/photos/andercismo/2349098787[10] http://commons.wikimedia.org/wiki/File:Open_24_Hrs_-_Money_Change_%284039347263%29.jpg

Gabriel GavassoProject Manager and Business AnalystASEAN expansion ggavasso@thoughtworks.com