So you want to make your organization Agile

This content is syndicated from George Dinwiddie's blog by George Dinwiddie. To view the original post in full, click here.

When I first discovered Extreme Programming a decade ago, I was a software developer wanting to produce the best, and best fitting, software that I could. In those days, it seems that most Agile adoptions were from the bottom up.

Now I find a lot of Agile adoptions are from the top (or, at least, middle) down. Managers have heard about the improved results that companies are achieving using Agile development, and they want some of that for their organizations. That’s not surprising, and it should result in both better results for the organization and better work life for the employees.

Unfortunately, it doesn’t always work out that way. What is it that goes wrong with these top-down Agile transitions? More importantly, how can a well-meaning manager conduct a successful Agile transition?

A manager used to working in a plan-driven manner is prone to some assumptions that can work against a successful Agile transition. I’ve never seen, or heard of, a transition that succeeded by defining a plan up front and then following that plan. It could happen, but it be luck that brought about the success. Instead, an Agile transition has to be steered to success. It has to be conducted in an Agile manner–a hard thing for a manager without Agile experience to do.

I’ve seen other managers go to the other extreme. Instead of planning their transition, they operate as if an Agile process can be installed like a new carpet. They order “enough Agile to cover the number of developer offices” and expect the Agile Coaching company to deliver the transition. There are several misconceptions common behind such an approach. One is that Agile is just for the software developers, and the portfolio management, the governance processes, and the involvement of both business and management can stay just as they are. Another misconception is that the transition itself is easy–just a matter of training–and people will change how they’re working because they’re told to do so.  Both of these misconceptions underestimate the effort required to make a transition, and are also deleterious to making a successful transition at all.

Enough about how to fail. How can we succeed in acquiring those Agile advantages?

For an organization of any size, planning the transition is essential. The plan, though, is not nearly as important as observing what happens, making adjustments, and re-planning as you go along. Thoughtful managers can anticipate some of the changes needed. If you’re currently using a waterfall approach with phase gates where further spending is justified, you’ll need to figure out an analogous process using functional slices instead of development phases. If you’re used to “capturing the requirements” in a document that’s shipped off to remote development teams, you’ll need to figure out ways to increase the interactivity between those deciding what needs to be built and those building it. These types of changes, whether anticipated or noticed during the transition, are highly dependent on the context of the organizational needs and the people involved. While there are many successful strategies, there are no easy cookie-cutter solutions.

Few managers are well equipped to anticipate the change process itself. This is a skill and knowledge area that’s not part of the day-to-day software development management needs. To most managers, understanding and managing change is not something they want to spend time and energy to learn–they’ve already got enough work on their hands. Yet it’s not practical to entirely subcontract the change management to an outside organization. Their leadership is essential in a successful transition. At the same time, a manager attempting a first Agile transition will have difficulty spotting some of the choices to be made–at least, spotting them before they become big problems. This is precisely why most managers are well-advised to get coaching for their Agile transition–not just for the development teams, but also for themselves.

You may think that this advice is entirely self-serving. After all, I am an Agile coach and I do this for a living. And, in a way, it is. You see, I’d much rather coach a wildly successful transition than a troubled attempt at one. But I’d rather you be successful whether or not you hire me as a coach.

But first, arm yourself with knowledge. Study up on what Agile is and how it’s done. Gain clarity on what you hope to gain from it, and what you know will have to change. Think about the relative priorities of these goals and changes, and of the risks involved. Forethought is a great ally.

But also think about the process of transition, itself. I recommend reading Managing Transitions: Making the Most of Change by William Bridges. This will give you some insights into the process of managing change in your organization, and some good advice.

Feel free to ask me for advice, also.

Leave a Reply

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

five × three =

There are 101 ways to do anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”



To explore how we can help you, please get in touch