Agile: organization, movement, or philosophy?

This content is syndicated from Agile Complexification Inverter by David Koontz. To view the original post in full, click here.

I referred to Agile today as a philosophy in a conversation with other Agile coaches.  I got a little push back.  So it made me think - is that the right word for the thing that has resulted from the Agile Manifesto

No.  I may want it to be a philosophy, and it may be my personal philosophy.  But it is not a philosophy that is recognized by the general population.  Nor even a philosophy as recognized by the IT industry nor software developers.

It is a movement.  Or is it a method of working?  I'm not sure - what's the difference? I believe that Scrum is a method of working, while I believe that Agile is greater than just being Scrum-y, or turning all the dials to 11 (XP).

However, if Agile were to marry Lean, then I think the union would have a great shot at becoming a philosophy.

So in my philosophy I try to marry the two movements and I think it makes for a philosophy.  One that has the capability to evolve via Double Loop Learning.  A philosophy should be capable of challenging it's own truth and modifying the goal to know the truth.  So in the manifesto the goal is to develop working software, along with all the necessary stuff like teams, and server farms required to deliver the software.  But is that the truth?  Is that the value stream result?  No. 

The ultimate goal of working software is to delight customers.  It is delighted customers that purchase the software.  Software has no real value until a customer chooses to purchase it or the device the software is embedded within.  Like the DVD player that really needs a better UX (no delighted customer here - no recommendation for that DVD player to my twitter friends).  A case in point is the eco-system that Apple has created with the iOS devices and the App Store.  Billions of dollars have not changed hands because of lists of acceptance criteria that have been met for thousands of feature sets.  Oh-no, it is because delighted customers have raved at the local watering hole that this app is awesome.

So if your company is looking to Agile to increase speed to market, or to double revenue in 5 years, or to increase quality while decreasing cost - then you are missing the movement.  And you will not make your transformation to Agile stick.

To make that Agile Transformation stick into the DNA of your organization you will have to promote the movement to a philosophy within your organization.  Then and only then will the movement (transformation) become capable of surviving the inevitable change of leadership and staff that will snuff out a movement.

My quest is to find the techniques that transform a movement into a philosophy.  But I need help.

Organization vs. movement vs. philosophy

An organization uses structure and resources and power to make things happen. Organizations hire people, issue policies, buy things, erect buildings, earn market share and get things done. Your company is probably an organization.
A movement has an emotional heart. A movement might use an organization, but it can replace systems and people if they disappear. Movements are more likely to cause widespread change, and they require leaders, not managers. The internet, it turns out, is a movement, and every time someone tries to own it, they fail.
A philosophy can survive things that might wipe out a movement and that would decimate an organization. A philosophy can skip a generation or two. It is often interpreted, and is more likely to break into autonomous groups, to morph and split and then reunite. Industrialism was a philosophy.
The trouble kicks in when you think you have one and you actually have the other.


Leave a Reply

What is 4 + 3 ?
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.”