Lessons in Agile
This post has been brewing for a while… I wrote it a few months ago and recently adapted it.
These are my thoughts and experiences over the years with Agile. You may not agree with them. That’s okay. Hopefully you take something good away with you.
Is Agile a framework or methodology?
I was recently asked this question in an interview. After years discovering, learning and working in Agile, I confidently replied,
“Its a methodology”.
I should have said, it’s a mindset.
I should have said it’s a bit of both.
I didnt get the job because there were more experienced candidates [Yes, I asked for feedback].
I needed to ‘check myself’ after that interview. Even though I know Agile.
Agile is a mindset, philosophy or way of thinking that is comprised of a set of principles and values (as outlined in the Agile manifesto). It serves as an over-arching umbrella for practices and frameworks that embrace those values and principles, such as Scrum and Kanban.
Lesson 1: Refresh your theory every now and again. Don’t get caught off guard like me.
The state of Agile
Ten years ago I felt people understood the values and principles of Agile. Since then, the world of work has changed.
Agile roles and job descriptions are different. Its a mish mash of traditional roles with Agile ones. Some without the right mindset. Some thrown into Agile roles without the relevant training or coaching. This is ineffective to business and detrimental to individuals.
The essence of Agile — to help people create a better way of working — to improve their work environments and meet the right business outcomes— is a bit blurry. Today that idea sits on the surface, in a checklist or presentation, but with little heart, truth or authenticity.
The people I first met in Agile were ones with heart, truth and passion. I was fortunate back then. They taught me — through their actions — what Agile is about. I walked away with not only knowledge but what Agile should Feel like. There are still those kinda people around today. I’ve met a few. But there’s also those who look the same, knows the theory, but present a dangerous promise — a cure.
What is a Snake-oil salesman?
Those who promise a cure for all your problems if you follow what they advise. They are strategic, they use all the right words, and they are everywhere.
There are a few Agile consultants who are true to their word. The ones who’ve been around a long time. The one’s you can trust. The one’s who take the journey with you and your teams . They don’t promise a cure and leave you to figure out the rest. Instead they paint a realistic vision, with practical coaching that is relevant for the individuals and Business.
Lesson 2: A failed Agile Transformation is costly to the business and its people.
Do your homework before transitioning. Get the right people on board who understand the heart of Agile.
Few things to consider before hiring an Agile consultant :
- Speak to at least 3 different consultants— like you would when getting a quote to reconstruct your house [in essence thats what you doing in a business when you transition the org and its people].
- Verify their Agile knowledge — like you would a Scrum Master for a job interview. If you don’t know Agile and it’s frameworks, learn it.
- If you already have Scrum Masters, let them work with you in hiring the consultant. Develop connections earlier on. They should work together with your teams.
- Watch online videos of these consultants giving talks. Notice how the audience responds to them. Better yet, watch them in person if possible.
- Find out who their influences are and why.
- Ask about the process — in detail — whats happens when they come into your organisation. State the problem and ask how they would approach it. [take special note of how you feel afterwards — every time you speak with them]. If something doesn’t feel right, it probably isn’t.
- Ask them to provide references of success stories — ask people at those referenced organisations how their experience was with these consultants.
Lesson 3: This is hard work. Laying down a solid foundation. It takes time. Most organizations don’t dig deep enough.
“Well begun, is halfway done!”
I don’t need to read a survey about ‘the state of Agile’ [most of which are created by snake-oil salesmen themselves].
Businesses signing up to Agile but not defining what success looks like in Agile, and regularly stopping to honestly inspect the results, learn, adapt. Agile is not an end state. Its a continuous improvement. Always with the people and the customer at heart.
“Agile must work”, they say.
Why ‘must’ it work?
Some businesses are not suited for Agile. And that’s okay! I honestly dont care what its called.
If one way is not working, try another. Does it really matter if its not Agile. You could be on the brink of a new methodology/framework that suits your business and people better.
You see… there’s two roads.
There’s the snake-oil salesman way — which is lies. And there’s the way it used to be and should be — truth.
The world of work has changed since 10 years ago. Greed is at the heart of business.
But…
Business is about people. The more we advance in technology and automation, the more we need to hold onto our values and principles as human beings. If we don’t. We just cogs in a machine. Nothing else.
Lesson 4: “Put your people first and you will reap the benefits.”
Agile is hard because it involves people and anything involving people is complex. In retrospect, anything accomplished that is hard, hopefully comes with results that matter. Mostly satisfaction in how its done — not only what was done.
Some do Agile in word only.
Some have been misguided.
Some do it for the money.
And some do it not even knowing Agile.
Wherever you find yourself, understand the meaning of Agile and get the right people to work alongside you.
