Agile Wars - And How to Avoid Them
By Barbara Roberts | 13 March 2018
At the heart of Agile, we value “individuals and interactions above processes and tools”. And yet for many years, the various Agile approaches appear to have been at war with one another. All too often, Agile is offered as a binary choice (“you are either agile or not-agile”), together with the recommendation that one Agile approach (usually the one being “sold in”) is all you need. I have also often seen a move to oust the established Agile approach with different flavour of Agile, regardless of how well the incumbent Agile approach is working – a “My Agile is better than yours” mentality. This all seems a long way from our original intention that Agile should be a collaborative, cooperative (and pragmatic) approach, targeted at delivering the best solution for the customer.
A Different Way of Thinking
Let’s look at this from a different starting point. Why would you limit your choice to a single Agile approach, when there is an opportunity to create a “best of breed” for your organisation by blending Agile approaches together? Every organisation is unique, although there will always be groups of organisations which face similar issues. So it is unlikely that the same single Agile approach will be equally suitable for a technology-focused software house, a complex product organisation, a global pharmaceutical organisation, an engineering manufacturing organisation, and a small start-up company.
Even inside a complex corporate organisation, the style of Agile may differ between different areas, as the issues faced are entirely different. I have run Agile transformations in large complex corporate organisation for many years, and for the vast majority of these the optimal solution is to create a “blended agile” approach – to ensure that the style of Agile being used addresses the specific issues for that particular organisation.
The Starting Point - A Simple Understanding of the Agile Options
In order to make informed decisions, a good starting point is to have a simple view of the pros and cons of the various agile approaches. And although there are now probably 100 different agile “flavours”, I am going to focus here on the most commonly adopted ones, and highlight some of the obvious strengths and weaknesses. This white paper is intended as a simple starting point to support decision-making for those who are not Agile experts. It is not intended as a detailed comprehensive analysis of each Agile approach, as full details are available elsewhere.
Read the full whitepaper