Our approach to agile implementations & agile consulting
So over the last couple of years of working with different companies implementing agile we have come to certain realisations around agile implementations that influences the way we approach implementing agile at organisations. We share some of the realisations with you here and under each of these realisations we will also highlight how we go about implementing agile.
The way we do it
We take agile frameworks and methodologies as a guideline and we adjust the approach to suit the client’s environment. The reason for this is that agile methodologies and frameworks are built for very mature organisations and are a bit of a perfect world / theoretical depiction. It is obviously good to strive towards these perfect world scenarios and have that as long-term goals, but the matter of the fact is that you will not be able to achieve that during your first few years of agile adoption.
Our approach focuses on getting things done!
Agile Implementation Realisations
Agile is a buzzword
Agile at the moment is a buzzword and all CIO’s basically want to implement agile (or so they say). Agile is like Cloud in this way, where most companies just jump onto the bandwagon of a new trend. This is the new thing and everyone seems to be adopting this, so surely we should too? No. Not necessarily. Is there a true understanding of what it takes to implement agile, how much of agile is my company really ready for and is this even possible to consider? How long will it take us to be agile and will we even realistically ever reach that? Why do I want to implement agile? What am I hoping to achieve by implementing agile and do I have measurable steps to ensure that I am doing the right thing?
So the right approach here is to evaluate how ready your organisation is to implement agile and what are the major stumbling blocks you have to overcome immediately or what changes you will have to make immediately to even start considering the journey of implementing agile. We thus require bold steps from the management and exec team we work with when implementing agile during the first few months.
So your main motivation for considering agile should be to streamline your environment and to achieve a level of optimisation and improvement in delivery. This is what we focus on at Infoware Studios. This does not mean that you are an agile organisation once you have implemented the first phase of agile. So this leads to the next point…..
Agile is a journey, not a destination
Your organisation will be at a specific point in its lifecycle. You have a specific culture, specific problems and a specific way of working and managing your environment. In order to become agile, you will have to take some initial steps towards becoming an agile organisation. As you mature your agile adoption you will take the next step and so forth and so forth. So this is really a long journey and the decision to take this on should thus be made with care. It does not help that halfway through you make decisions that counters your investment to adopt agile.
You will thus need a long-term commitment when deciding to implement agile. It is not a quick fix. It is a commitment. Proper roadmapping and mapping this to your organisation strategy is what we help with. We work out this roadmap with you. This roadmap could be a 3 year goal and plan. Then even after the 3 years you will continuously have to make more changes and improvements to stay on track.
In agile we self-organise
Most companies will never self-organise and this is a fact. The reality is that in order to truly self-organise each and every person in your organisation needs to take 100% responsibility for their work and how their work / role contributes to the bottom line. Most people do not even know how the company is performing financially. Each and every person also needs to invest effort into removing personal blockages, fears and shortfalls.
So bearing this in mind, we believe in project management disciplines within agile and a Scrum Master having strong project management skills. Although the team does not report to the Scrum Master necessarily, the Scrum Master is responsible for guaranteeing the success of the team and applying good project management principles and disciplines. This is also a key strength of a Product Owner.
Further to this, self-organisation requires a specific awareness in the individuals working at the organisation. This can only be achieved if a certain level of personal development is done. And this personal development is not on a skills level, but on a very personal level to increase this awareness.
We help here to take the key leadership team and other identified people in an organisation on a tough personal growth journey where they have to face their hardships and issues in order to be free from this influencing their success and the success of your organisation. We all bring into the organisation landscape our own personal issues and the ability of your people to operate effectively and efficiently will be influenced by these personal hardships. Leaving your personal issues at home… Not possible.
This forms part of our change management / transformation services.
Agile is a process
So yes, most agile methodologies and frameworks focus heavily on process and then there are of course the fluffy soft values that they indicate we should aspire to. Implementing an agile process alone will definitely get you some improvements. Implementing only an agile process will not solve all your problems. Implementing the agile values I have never seen as this means that these values needs to be embedded into your organisational culture.
So implementing an agile process is not making you agile.
So we focus on all things that affect your organisation: culture, values, incentives, technical constraints and use agile as a way to manage your processes. You will often find that there are lots of other things that prohibits your ability to become agile.
We help you to identify all of them. What you decide to tackle is up to you.
Management in Agile
Agile frameworks hardly specify anything around management. And why? As this is against the principle of self-organisation. The reality is that no organisation is self-organised and on your journey to achieve this goal (that you might never reach) you need to put the safety nets in place to guarantee your organisations profitability. Unless your organisation is 100% self-organised you will need managers. So what is the job of management in agile? To manage inefficiencies and get people to take responsibility. If we had no inefficiencies in organisations, then only will we not need managers.
We assist you to align your organisational structure and team construction with agile and you will follow a long-term plan to achieve this.
Agile and optimisation
We play the role of recognising the inefficiencies, highlighting it to you and coming up with a plan to overcome it. Once we leave, you will have to invest into a person that can play this role continuously in the organisation as this is the only way to not get complacent. Your process owners and product owners of course forms part of this team and should have this responsibility, but they also have to have the skills to do this: to spot problems and facilitate solutions and improvements to overcome this.
Optimisation over agile
So we basically value optimisation over agile frameworks and methodologies and we have a unique approach to agile adoption in organisations. No one organisation is the same. Organisations might face the same problems but the mere fact that different people work at each organisation makes it impossible to take a cookie cutter approach to agile implementations.
As the hardest part to change is the organisational culture and dynamics, you need to be committed to changing your organisational culture if you are serious about implementing agile. If you are not prepared to do this, then do not attempt to implement agile as all you will be able to achieve is using a different process or way to manage things. Changing your culture will mean developing your people on a personal growth level. From CEO level down.
We have specific ways we deal with facilitating this change. Call us to find out how we do this.