Skip to main content

Agile Australia 2011 Series - Sustain your Agile Transformation

Move at a pace you can sustain, and a price you can sustain.

It’s much easier to take baby steps then make a wholesale radical shift and zap your organisastion into Agile overnight, but it does come at a cost. The price you will pay is that during your slow and steady change program your software won’t be cheaper to build and your efficiency won’t be optimised. So you will carry some costs of inefficiency while you are in a transitional phase.

Why not make the move to Agile Transformation in a radical wholesale manner if it would maximise your efficiency and give you best possible return for your money in the shortest time? Well there are many reasons, and it saddens me to say I’ve experienced all of them in the past. In many ways this is a very sad topic for me as it encapsulates all of the frustrations and limitations I’ve felt in our own agile transformation.

Reasons not to blast through with radical transformation can include:

  • Your management doesn’t believe in the empirical efficiencies that can be gained and need to have it proven to them
  • Your organisation is not comfortable with radical change and you feel a lack of confidence in initiating such a change, could be; a highly regulated industry, old industry or even that your role is not massively influential
  • The culture wouldn’t support agile and you feel you must be stealthy, could be; a lack of trust, a blame culture, political environment, or large ‘enterprise wide’ factions exist that will block you

How can I offer you hope on this topic?

· Be realistic about what resources are available and what outcome you can achieve.

If you have a small budget you might just have to move slowly. For us we tackled process first, and development practices such as TDD and ATDD have come at the end, it’s not ideal but it was completely sustainable for us and fitted within our context of a legacy platform, a few skilled agile resources and very small budget for agile learning.

Our model was do a pilot project and asses. Then we did another project and assessed that one. One by one we then transitioned each development stream to using the same agile approach until our 8 concurrent streams were all working in this way.

This addresses the ‘unbelieving management’ syndrome as you can prove an agile success in a pilot situation. In addition it proves that a different approach can work in your organisation, addressing the fear of change and perhaps the unsupportive culture. You can build a positive culture in one team that will make Agile work, and then proving it to yourself you can move forward with baby steps, building on each success and promoting success vigorously each time.

If I came across agile people buried in their organisation thinking that they can’t make a change I would recommend starting small and moving sustainably, after all, baby steps are still steps in the right direction.


Popular posts from this blog

Business Requirement Documents are just no good and should be abolished from the world of creating software

I had hoped the world could have wholeheartedly rejected Business Requirement documents by now. For too long I’ve seen the repeated scenario of only commencing the creation of a new initiative with a requirements document.Unfortunately most organisations that have teams developing software still use these flawed anathemas to creativity as the status quo. Despite agile approaches maturing and customer-centric modes of design emerging, requirements documents still persist. 
If you work in an organisation that doesn’t use business requirement documents any more, read no further. You are lucky; sense has prevailed at your place however in my experience, you are still the minority.
Let's face it; addressing this issue is not always the point you want to start your improvement work when there's much that could be dysfunctional with how a team is delivering software. But now, I find myself as mad as hell, and I'm not going to take business requirement documents anymore. I want to …

Gamify your children

Inspired by James Ross’s LAST conference talk on The Shamification of Lamification and the Reclaimification of Gamification I was motivated to try and “Gamify” the school holidays for my three children, Leo aged 8, Chloe 9 and Max 10.
Buy-in is everything, so the first thing we did was a quick workshop to extract the kids ideas. I asked them to write their ideas for good rewards on sticky notes, with a few examples for context, such as ‘trip to the movies or ‘play date with a friend’ . They had 5 minutes to come up with their ideas – one idea per sticky note (as always).
They then read out their ideas for all of us to hear, there were a few duplicates and also a few comedy suggestions. Even though we had ruled out crazy stuff, such as rewards of a million dollars, Leo had written down ‘A unicorn for the back yard’ reading it out with gleeful giggles.
Then they spent 5 minutes writing down tasks that they could do to earn rewards. By now they had the hang of it and quickly came up with t…

Agile Australia 2011 Series - Agile Governance

If you are in an industry that is heavily into governance you need some structure and process around your projects or you could find your Agile projects getting usurped by the culture of command and control. So it’s important not to shy away from the topic but to work with the entities that enforce and monitor governance. In this way you can create something that is fast and easy and not laborious to work with.I work for an Apra regulated organisation and we made keenly aware of our obligation under Apra to evidence documented change when audited. However in all organisations I’ve ever worked in, there are boundaries that bend quite a bit, ways to change things and ways to get by that satisfy governance process without crippling your agile process.There’s almost two alternating schools of thought here which are ‘work within process’ and ‘decide to change the process’. It’s actually pretty easy for my team to work within process. Project approvals, mandates and PIDs that are important …