Agile Transformation

This content is syndicated from Agile & Business by Joe Little. To view the original post in full, click here.

I have already started, but want again to continue talking about an easy subject: Transforming a company to agile. Well, not so easy. But not as hard as some people think. 'A journey of a thousand miles starts with one step.' We are too easily discouraged by what seems a daunting task. We too readily make the mental mistake: "I have to have it all figured out before I can start." Sorry, but when working with people, you should know by now that 'having it all figured out' is not a notion even worth talking about. You cannot, you should not, and you will never control other people. Still, there are things we can learn and things we can do better to make (or influence) how the agile transformation will unfold. I said you were not all powerful. That is not the same as saying you are completely without influence and smarts and wise things to say and do. You are a Jedi. We are starting to build a course on how to do agile transformations. Some basic notions: * change in organizations is hard (but far from impossible) * there is much existing knowledge on how to get change to happen and how to get it to stick * this knowledge is not simple * agile transformation in some sense affects 'everything' * it is necessary to make a list (of work to do) and prioritize * for many reasons, it is useful to work as a 'transformation team' * it is useful to learn some theory. Put another way: trying to learn from experiences at other places * it is useful to learn and do and get feedback and repeat (PDCA) executing the transformation * top-down or bottom-up? Yes!! * although there is no 'one size fits all' answer, there is a basic framework, and some very common patterns * for an agile transformation, our bias is that all change agents (well, god, is that the world's best term or what?) must actually understand, in a real way, the key stuff they are recommending changing to. Ex: They should have actually been in a Scrum team, as a pig. * 'people don't resist change, they resist being change'. * for more than one reason, in general we want the 'objects' of change to take some decisions about what the change is. (Freedom: what an original idea in American corporations!) This is not a stupid 'everyone is exactly equal' notion. Nor 'let's find the stupidest guy around, and let him decide everything.' Perhaps more to discuss. Some notions about the course. * the course is only useful if it helps 'the change' get more results. Just teaching some people is not enough. * we define change agents broadly * the course discusses some key concepts and theories * the course does exercises * a workshop, practical and specific to your situation, is included * basic patterns of new idea adoption * setting a scope for a transformation team * determining the effectiveness of a transformation team * what is a reasonable price for agile transformation? * how do we convince the 'buyers' to take the plunge? How convince them to continue to invest? * where does communication fit it? How do we know we are doing the right amount and doing it effectively? * what are some tools and methods the transformation team can use to 'make' the transformation happen? * how does the transformation team identify emerging impediments to the transformation? * is there a connection between the transformation team and the 'real' agile teams? If so, what and how? * is there a connection between the transformation team and other groups in the firm? If so, what and how? * how does the transformation team do and explain 'adaptive planning' for the transformation? * how does the transformation team measure success? * what about scaling? * what about transformation in multiple locations and time zones and cultures? These are initial thoughts. Your thoughts?

One Response to “Agile Transformation”

  1. Martin says:

    Been finding several broken links on this blog including this one

Leave a Reply

What is 8 + 5 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

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

What People Say

“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.”


“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.”


“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 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!”


“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 was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“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. ”


“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.”


“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 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.”