Agile Eastern Europe 2011 Large Scale Agile Transformation

Large Scale Agile Transformation Agile Eastern Europe: Season 3 Kiev, Ukraine Sept 23 & 24 2011

The Story of A Large Scale Agile Transformation Agile Transformation Petra Skapa

Questions…
How many of you are or have been part of an Agile team?
How many of you have been part of an organization transitioning to Agile?
How many of you have had the job of helping organization transition?
© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com

Once upon a time...
..in an Agile Transformation far far away…
© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Agile Transformation Petra Skapa

Chapter 1
...there lived a prince who wanted his castle to be grander, his land to produce more crops and for all the people to be happy.

Chapter 2
The prince decided to go on a long long long journey to seek the answers to his dreams.
He attended gatherings (like AgileEE ), met new cultures and discovered a magic chest called Agile that might provide the riches he dreamed of.
© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com AGILE

Chapter 3
The prince opened the chest and out popped an Agile coach
The coach and the prince
worked together for many
moons, and this is their story..

Interlude
4 x 4 teaser
4 companies 4 questions
1 deep dive
Why did they want to ?
How was it done?
Are they Agile now?
Was it worth it ?
© 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Agile Transformation

Why did they want to transform to Agile?
Long time to market
Delivering the wrong thing to customers
Desire to scale
Low quality = high maintenance costs
Losing market share
Brain drain
They used to be innovative, less now
It’s cooool, it’s in style

2003 © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Question Answer 2. How?
Hired experts
Pilot project
Right people on the bus
Continuous integration on legacy code
Strong sponsor, leader of department
Took risks, willing to fail
3. Agile now? B, they did a second wave, tried again and continue to move forward 4. Worth it?
Significantly reduced time to market
Continued expansion of Agile

Centralized support
Just do Scrum at scale (by the book)
Local leaders with some control
Agile partner consultants
3. Agile now? in progress, pockets of agility 4. Worth it?
Visibility increased
R&D and Product Mgmt as partners
Increased focus on value
First ever “0 bug release”

2 consultants
Create documents
Check and enforce adherence
No team contact, training only
3. Agile now? No 4. Worth it?
No change
But still rich

We asked, why change?
Unsustainable pace
Scaling challenges
Couldn’t meet demand
Big future vision

We listened to people
Imposed Deadlines
Lack of clear requirements
Waiting on other teams
Integration with other systems
Testing is an afterthought
Poor communication
Context switching, multi tasking, re-prioritizing

We looked at the code
It wasn’t pretty

We looked at the code
15 manual steps to prepare a build
Deployment failure 50%
25% test coverage
0% of tests run automatically
30% code duplication
100s of methods over 150 lines
Files over 2000 lines

We identified themes for improvement
Lack of Communication and Collaboration
Lack of Disciplined Testing Practices
Lack of Clearly Defined Roles & Responsibilities
Too Many Manual Processes
Undisciplined Project Initiation

We made recommendations
Pilot Project
Put in iterations
Teach coding best practices (XP)
Metrics
Communication
Roles clarity

We developed a change model © 2011 Petra Skapa, All rights reserved, petra@alluvial-consulting.com Agile Guidance Team Chief Agilist Backlog Owner Strategic Direction Employee Employee Organizational Owners Employee 1 Employee 2 Employee 2 Agile Training 101 Agile Cookbook & Inception Toolbox Agile Health Check & Assessment Project & Story Sizing Iteration Management Employee External Expert External Expert

We ended with continuous improvement
..and all the riches that brings
Based on Lean thinking

Was it worth it?
“ I would never go back to how we worked before”
Major brand expansion
Destination employer

Epilogue – Know Why!
Don’t embark on an Agile transformation because you want to ‘be Agile’,
do it because you want to…
Make more money
Beat your competitors
Delight your customers
Retain your people
Innovate

And once you know why, then..
Accept their will be a learning curve
Change is hard
Have a holistic approach
System thinking
Find out what is most important to do first
Find the biggest pains and wastes
Invest time, experts and potentially tools
People need support to change
Think continuous improvement

Thank You! спасибі

Agile Eastern Europe 2011 Large Scale Agile Transformation

by pskapa on Sep 26, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

1 Embed 199

Statistics

Agile Eastern Europe 2011 Large Scale Agile Transformation — Presentation Transcript