agile adoption - opportunities and challenges

Service Result Knowledge

Agile Adoption: Opportunities and Challenges

3 February 2011Silvana Wasitova

2

To Do Doing Done

© Itecor all rights reserved

Opportunities

Examples

Challenges

Strategy

I little bit about me


Waterfall

Scrum

At

4 © Itecor all rights reserved

5

To Do Doing Done


Opportunities

Examples

Challenges

Strategy

6

Rarely19%

Never45%

Always7%

Often13%

Sometimes16%

64% implemented features are rarely or never used

Ref: Jim Johnson, Chairman of Standish Group, quoted in 2006 in: http://www.infoq.com/articles/Interview-Johnson-Standish-CHAOSSample: government and commercial organizations, no vendors, suppliers or consultants

Focusing on customer needs ensures:

the right features are builtnot wasting effort (and resources) on features that are not needed

Main principle:Only build the features that the client/users need


http://www.infoq.com/articles/Interview-Johnson-Standish-CHAOS

© Silvana Wasitova

Scrum vs. Waterfall: Time To Market

Develop & QASpec

Develop & QA + Changes

SCRUM

Waterfall

y wks

CollaborativeResults-Oriented

3 MONTHS

x wks

Faster Time to Market Higher Quality Satisfied Customer Better Usability

Spec

6-10 MONTHS

Changes

Sequential Process-Oriented


Lower cost of change

Cost of change

Traditional project

Agileproject

Time•More defects prevented &

fixed •Continuous testing•Fast feedback & adaptive

planning

9

Agile deals with


•Specifications will never be fully understoodZiv’s Law

•The user will never be sure of what they want until they see the system in production (if then)

Humphrey’s Law

•An interactive system can never be fully specified, nor can it ever be fully tested

Wegner’s Lemma

•Software evolves more rapidly as it approaches chaotic regions (without spilling into chaos)

Langdon’s Lemma

10

Why Scrum works


1. Close collaboration with client (or proxy) better productincreased satisfaction

2. Transparency through daily check-ins: early visibility of issues early resolution reduced risk

3. Increased ROI: delivering business value in small increments, more often

4. Eliminate waste, focus on highest priorities

5. Inspect, adapt, improve: in each iteration

11

To Do Doing Done


Opportunities

Examples

Challenges

Strategy

12

Scrum Adoption at Yahoo


2004: VP of Product Development authorized experiment with scrum2005: Hired Senior Director of Agile Development2008 status:

3 coaches, each coaching approx. 10 scrum teams/year200 scrum teams world wide, total approx. 1500+ employees

Results in 2008:Average Team Velocity increase estimated at +35% / year,in some cases 300% - 400%

Development cost reduction of over USD 1 million / yearROI on transition and trainings about 100% in first year

Note: In those first three years, 15-20% of people consistently DID NOT like Scrumhttp://agilesoftwaredevelopment.com/blog/artem/lessons-yahoos-scrum-adoption

http://agilesoftwaredevelopment.com/blog/artem/lessons-yahoos-scrum-adoption

13

Scrum: New Effectiveness: 27.25/50 = 54.5%Increase by 430%

British Telecom 2007, http://scalingsoftwareagility.files.wordpress.com/2008/06/scrumbt-v14.pdf

Typically BT Value Stream


http://scalingsoftwareagility.files.wordpress.com/2008/06/scrumbt-v14.pdf

14

HCL EAI Services Inc.


Enterprise application integration services: healthcare, retail, telecommunication, wireless.

http://www.bspin.org/archives-folder/03%20Krishna%20Prasad.pdf

All bugs are fixed for the release

All high level bugs are fixed for the release. Medium and low level bugs are not fixed

Product quality index

Client feedback

Burndown ChartNoneVisibility toolsProgress tracking

4070Average working

hours/week

6040Defects fixed

53New features

Increase in productivity

Release with ScrumRelease before ScrumMetricCategory


15

Salesforce.com - 2007

http://www.slideshare.net/sgreene/salesforcecom-agile-transformation-agile-2007-conference

Down to 1 release/yrScrum adoption: 3 months

Results:

60+ Critical features delivered in < 9 months

“Idea to Release” avg. rate: 2.2 quarters

70% of “Top 10 Ideas” are on track for delivery in 2007

16

Salesforce.com - 2007


17

To Do Doing Done


Opportunities

Examples

Challenges

Strategy

Challenges: Mindset Change

Crossing the Chasm, Geoffrey Moore, 2002

Will this work?

I want to try!

I heard of this new thing

Do I have to?

People are talking about it

Coaching Helps

Innovator Early adopters Early Majority Late Majority Laggards

Th

e C

has

m

© Itecor all rights reserved 18

19

MINDSET CHANGE


20

Barriers to Adoption


http://www.versionone.com/pdf/3rdAnnualStateOfAgile_FullDataReport.pdf


21

Causes of Failed Adoption




22

To Do Doing Done


Opportunities

Examples

Challenges

Strategy

Keys to Successful

Agile Adoption



Christopher Colombus

Visionary &Champion


Queen Isabelle

Sponsor


Rosetta Stone

Translation Key


Coach Extraordinaire

Trainer & Coach

Agile Champions




Strategy: A.D.A.P.T.


Strategy:

•AWARENESS that the current approach is not workingA•DESIRE to changeD•ABILITY to work in agile mannerA•PROMOTE early success, build momentumP•TRANSFER impact toother parts of organization, to stickT

Mike Cohn, MountainGoat Software

What Works


Start small, then grow

32

Train, Raise Awareness


Build Organizational Support

all directionsat the same time

Top Down

Bottom Up

Horizontal


Teamwork


Align Incentives


Inspect, Adapt


And one more thing…

That 10x hyper-productivity...

it only comes if serious

about removing real impedimentseven some sacred cows

COURAGE


Silvana Wasitova, PMP, CSM, CSP

Vevey, [email protected]

+41 79 558 05 09

mailto:[email protected]

http://scrumalliance.org/

42

References


Salesforce.com Scrum Rollout Results, 2007http://www.slideshare.net/sgreene/salesforcecom-agile-transformation-agile-2007-conference

Yahoo Scrum Rollout Results, 2008http://agilesoftwaredevelopment.com/blog/artem/lessons-yahoos-scrum-adoption

BT Scrum Rollout Results, 2007http://scalingsoftwareagility.files.wordpress.com/2008/06/scrumbt-v14.pdf

VersionOne Surveys http://www.versionone.com/pdf/3rdAnnualStateOfAgile_FullDataReport.pdf

HCL EAI Scrum Rollout Resultshttp://www.bspin.org/archives-folder/03%20Krishna%20Prasad.pdf

Crossing the Chasm, Geoffrey Moore, 2002“ADAPT” – Mike Cohn, MountaingGoatSoftware.com The Heart of Change: Real-Life Stories of How People Change Their Organizations (2002) and Leading Change (1996), John KotterOrganizational Patterns in Agile Software Development, James Coplien & Neil Harrison



http://agilesoftwaredevelopment.com/blog/artem/lessons-yahoos-scrum-adoption

http://scalingsoftwareagility.files.wordpress.com/2008/06/scrumbt-v14.pdf



agile adoption - opportunities and challenges

Technology

me3 itecor

consultants itecor

done2 itecor

done5 itecor

at4 itecor

lower cost of change8

right features

customer needs