Some months ago, a teammate suggested that I should write something about agility outside traditional environments (software and IT organizations). And I thought: “It’s a great idea, it’ll take me just a couple of hours.” My motivation was high when I started writing, but with each line written, I realized it wasn’t going to be a short task. I therefore decided to break down this long text into a set of (more or less) short chapters that contain my point of view regarding agility outside digital environments. My aim is to help you answer the main questions people have about this issue.
Let me start with a personal thought. I am a bit tired of repeatedly hearing the typical “We are living times of quick and complex changes, Industry 4.0 is changing everything, bla bla bla…” as easy excuses to sell or launch an agile transformation plan. The fact that everything is changing very quickly is obvious. The context in which companies are competing today is quite different to that of some years ago, and in the years ahead it will change again. Digital and business transformation are changing our way of life, our way of working and our way of thinking. However, we need to control the panic.
Should we all go crazy and (try to) apply Agile like a magic potion that will transform our traditional business into a blue chip organization, like a toad becoming a handsome prince after being kissed by a princess? It´s well known that an agile mindset – and you can find several references about it – can be implemented in IT or digital development environments using different frameworks (like Scrum, Kanban, XP, etc.). However, what happens when the exotic idea of changing the entire business process is not specifically related to the development of digital solutions?
Let’s take a step-by-step approach to such cases, bearing in mind that all these thoughts can also be applied to an IT environment.
No, this is not a trick question. We need to think about our needs. Being agile by applying a certain methodology or tools (e.g. Scrum Events) is easy, but to be truly agile takes a HUGE effort. Achieving genuine agility requires a big cultural change not just new roles, processes or a methodology. The transformation process may have a huge impact within a company. This must be carefully analyzed because it requires investment not only in terms of money, but also in terms of the personal effort required from employees and collaborators.
Agile emerged due to the need to maximize the value returned by teams in a changing context in which flexibility and speed are required to reduce time to market. In that context, Agile really makes a difference and returns additional value. You can redefine almost any process based on an agile approach, but the question you need to answer is:
What will be the real ROI of the move to Agile?
You can probably start (and finish) your agile transformation plan by answering this question using the following Agile principle:
“Simplicity – the art of maximizing the amount of work not done – is essential”
Launching agile transformation initiatives requires the right balance between the cost of the transformation, the impact it can have, and the sustainability of the changes within the business affected by those changes (people, processes, organization).
There could be solutions other than applying an agile approach that bring you closer to the market and customers or eliminate economic restrictions. I am referring to Lean initiatives for example, which result in improved efficiency. Lean techniques help you to reduce the waste of processes so that you can achieve good results. Although Lean also has an impact on a company’s processes and culture, the changes may be a little less radical. We can’t forget that Agile is derived from Lean. In other cases, once you have analyzed your context and you still consider that optimizing is not enough to achieve the results you need, you can start thinking about Agile.
Once you understand what investments are required to become agile, the expected benefits, and if it is worth it, it is time to analyze what exactly you need to do and how you can do it. You can then start the transformation.
I am trying to explain how to do this outside traditional IT processes. So, forget everything about IT, we will not be focusing on it – and there are thousands of articles addressing it on the internet. In my opinion, almost any business process that requires agility can be transformed. But to do it right you have to keep in mind the Agile Manifesto and Agile Principles. These values and principles involve several concepts, but in terms of agility outside IT I would like to focus on the following:
If you want to become agile in your business, but don’t want to become another group of people doing things the wrong way and calling it Agile practices (sticky notes everywhere), you will have to keep the above concepts in mind.
Perhaps your business needs to be agile, but your organization requires deep changes in terms of cultural behavior, reorganization, etc. Maybe a business process needs to be agile, but the company or your department is not willing to provide the resources and context needed to achieve agility. In such cases, you can start looking for the right sponsor/s to empower the initiative. If you think that the department, functional area or company where you want to start the transformation is not ready, the best thing you can do is to work on building the required environment before continuing with the next step. Trying to develop an agile transformation plan without the right context is frustrating and self-defeating. Working on top-management awareness, looking for a strong leader to support the transformation, and acquiring the necessary resources are the best suggestions I have for you.
Well, here we are, exactly where things happen. You know that you need the transformation and, fortunately, you are empowered to realize the needed environment. Now what? Before starting to change anything, you need to identify some concepts within your business processes:
In the following weeks, I will share my thoughts about these topics, one by one.
Next chapter: Enterprise Agility – No value, no party
Chapter 3: Enterprise Agility – Finding and managing business process boundaries
Chapter 4: Enterprise Agility – Help me help you!
Chapter 5: Enterprise Agility – Agile teams, those who make the things happen
Chapter 6: Enterprise Agility – Prioritization, taking an economic view
Chapter 7: Enterprise Agility – Collaboration as a key success factor