Agile Transformation (1)

I was leading an Intermediate CSPO course last week in Winston-Salem.  Some good questions. One theme was about the agile transformation.

The idea is simple, and has many names.  One way to say it: Only by transforming the culture and many of the current ‘ways of doing things’ can a firm realize the fuller value of lean-agile-scrum.  So, a couple of related sayings:
“Culture eats strategy for breakfast.”
“Once you implement Scrum, everything must change.”But before I discuss those (both are useful, but neither fully correct) — let me discuss what an agile transformation might be.Most firms typically start with one or two pilot Scrum teams.

Then they expand to say 5 Scrum teams.

Then they can notice that a few managers are working on the impediments of the five teams.  And someone suggests an “impediment removal team” composed of those managers. And that they act like a Scrum team, except that their product backlog derives from the impediments of the 5 Scrum teams.

Then they decide to expand to more teams.  And now people start noticing, in a bigger way, all kinds of impediments that are ‘cultural’.  How we compensate people, who reports to whom, performance appraisals, management metrics, how different departments interact, etc, etc, etc.

People also notice that starting teams is serious effort.  Training is costly and difficult to arrange for lots of people. The teams should have agile coaches; how does that get arranged.  The teams need team rooms.  How do you control that old teams don’t revert to waterfall.  Are the managers (business and technology) truly understanding the goals of agile?

And the firm hears that other firms at this stage underwent an “agile transformation”.  And they wonder what that means and how they might do it.

We, and lots of experienced coaches, recommend an ‘agile transformation team’.   The concept here is some more senior managers take on “transformation stories”much like a Scrum team would.

First, we strongly favor this approach, but it is hard, and it must be done professionally.

Some problems with this:
1. Stories are vague or huge.  Example: “Change the waterfall mindset.” Nice idea, but how would you ever prove that you did it?
2. The Team is senior people.  Meaning, that they have forgotten how to work as a real team, and they have forgotten how to do ‘real work’.  But some senior people are needed, or this team has no clout.
3. The Team is mostly senior people.  Meaning: who will do some real work. We recommend having some less senior people on the team, who will do more real work.
4. How do you measure the team’s productivity?  This is hard, but if they can’t show somehow some “data”, then how do you decide if the benefits are worth the costs?

Two more key ideas:
A. There should be leadership from the top.  If we are talking about GE, maybe Jeffrey Immelt does not have to ‘preach’ agile, but someone pretty senior does.  To get the most benefits.
B/ There should be leadership from the bottom.  The senior guys are much more comfortable pulling agile if they know ‘real people’ also like it.  Leadership from the bottom means an enthusiasm to build and expand agile. An to take some actions to make that happen.

A start on this huge topic…

Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Posts

Six Actionable Nuggets of Advice for Becoming a First-time Technology NED

If the pandemic has taught companies anything it’s that tech is not something that you put off and think about ‘later’. The last year has seen organisations go through huge digital transformations, whether planned or otherwise. And for those that aren’t technology-based companies, getting the right board-level advice can not only be hard to find, but the difference between success

Read More »

Culture, Skills, and Capabilities // How to become a more data-driven organisation

In our whitepaper “How to become a more data-driven organisation”, we wrote about the five steps that an organisation would need to take, which are: Outcomes: Defining goals and metrics to ensure clear and measurable outcomes Analytics: Implementing and sharing the analytics to improve data-driven decision making Innovation: Testing assumptions through hypothesis testing and learning Data Platform: Gaining new insights

Read More »

Data Platform // How to become a more data-driven organisation

This is the fourth article in our series on “How to become a more data-driven organisation”, and we are going to be focusing on Data Platforms. It is at this point that most people start to dive deep into the technical aspects of Data Lakes vs Data Warehouses, but we want to bring us back up a level and ask

Read More »

Search the Blog

Agile Management Made Easy!

All About Agile

By Kelly Waters

“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”

Kelly Waters

Agile 101 is available to purchase. GAME ON!

Agile 101

Emma Hopkinson-Spark

“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark

Why did we make the game?

How to play the game?

London

101 Ways Limited
145 City Rd
London
EC1V 1AZ
United Kingdom

Amsterdam

101 Ways BV
Weesperstraat 61-105
1018 VN Amsterdam
Netherlands

Contact Us

If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at contact-us@101ways.com.