Agile. It’s a term that’s being used quite a lot recently as industries, other than software programming from where it began, are beginning to adopt its methodologies.
For those who are quite new to the concept, Agile is a methodology that was first created formally in software programming in the early noughties. From my passive understanding of it, it’s essentially an incremental delivery of a product that evolves as a living thing that can be adapted, revised and improved on, so to be produced on time and on budget.
Rather than wait for the T’s to be crossed and the I’s to be dotted, getting something workable out there on time and on budget means that work can continue on a manifested product and much more collaboratively.
This has many benefits, too many to go into, but I wanted to focus in on my particular favourites:
- There is a product produced on time. As someone incredibly impatient and more of a big thinker rather than a detail-delver, I like to just get things out there. No dillying. No dallying. No faffing with minute details that, in the grand scheme of things, aren’t worth delaying a project for. Where things are produced that aren’t polished, the end users are of course made aware of this. Which leads me to my next favourite benefit…
- When the product isn’t polished, there’s room for improvement and collaboration. An idea looks great on paper but when it comes to life, you spot new flaws and gaps that couldn’t have otherwise been picked up. So if the end result was delayed drastically for the irrelevant finishing touches, it becomes absolutely superfluous if it’s not fit for purpose or the end user notices something that needs sorting. Having it out there means it is a live demonstration, one that can be adapted, amended and revised. It also means it can evolve in its natural habitat, ensuring it’s fit for purpose. The time spent on dallying can instead be spent on improving.
This can be seen as a sort of beta test, trying out an unfinished product to identify flaws and receive feedback.
The agile concept was formalised in the early noughties, as I’ve mentioned, but I’ve found a reference to the particular elements listed above many years before this.
In the book “Training needs analysis and evaluation” by Frances and Roland Bee (1994, Institute of Personnel and Development), there is a delightful analogy that demonstrates an agile approach to addressing an issue. This isn’t word for word but goes a little something like this:
The Town Planner
A town planner was given the task to place a park in the middle of the town that had a pathway and flowers. Previous designs involved paths being in pretty symmetrical patterns or where the skilled planners felt most appropriate. The problem with previous attempts though was that pesky walkers would ignore these carefully thought out paths and walk over the grass and flowers, creating their own shortcuts.
This town planner felt a bit rebellious though and tried a different approach. They placed the park in the centre of the town, as agreed, and then opened the park to the public. No flowers and no paths.
With a bit of scepticism, they were left to it and after a couple of months the town planner returned to their park.
They discovered the walkers and town folk had worn down their own paths that they felt were the best way to get from A to B.
The town planner then proceeded to put down paths based on the town folk’s worn down paths.
This is a great example of getting something out there and seeing how it goes when producing something is far more important if not more beneficial than having it polished first.
It’s not a cop out; it needs to be sensible and able to improve itself by being ‘alive’ and out there. Off of paper and into the real world in order to learn the practicalities from living its purpose and evolve.
So what does this mean for you in the workplace?
I anticipate more organisations jumping onto the Agile bandwagon; it’s practical, it keeps momentum, and it contributes to delivering results.
If you were to start practising this methodology in the work that you do, you should be able to demonstrate the benefits it has to your team and your organisation if they haven’t already adopted it.
Figuring out when to apply the approach though is something you will need to assess per project or task. Weigh the positive and negative impact on producing what can be seen as a half-finished product on time, with producing a finished product out of time.
Sometimes it’s necessary to polish things off before producing it and the extra time that needs to be negotiated will make sense and be more beneficial.
However, make sure this isn’t an anti-Agile mindset. For those who like to take a disproportionately long time faffing with small details won’t like this new approach so you will need to pick the right tasks to demonstrate the benefits of Agile.
Start with baby steps and with products with minimal impact that are ‘semi completed’. It may be a new concept for you too so make sure you get comfortable with it and record the positive impact and benefits it has before spreading it wider.
You can also apply this mindset to your career planning and management. You might not necessarily know the specifics of your end goal (ideal career choice, the niche for your own business, progressing your career, leaving a job) but you can begin to take steps in the right direction.
A squeaky polished career plan can be edited, revamped or even completely trashed as you progress through it, and decide to change your end goal or your efforts, as I’ve written about before. This is usually as a result of having taken those first baby steps into the plan, bringing it to life from just a sensible-sounding idea on paper.
Yes, you might change direction, but the skills and the things you have learnt during those initial stages not only set you up to the correct path (even as a process of elimination!) but they’re also transferrable to the correct path.
It’s essential to begin this evolution process. This can only begin with a half-finished product that has room to grow and developments without the restrictions of a polished final product.
Whether this is a project at work that seems to be stuck or your career plans that are putting your actions on hold, begin with the first few steps and see how they evolve to the final product.
Do you want to carry on the conversation and leave a comment, or just say hi? Come on over to my social accounts and have a chat there – you’re more likely to catch me in those neck of the woods! The links are at the top of the page. See you soon!