Skip to content
Our website will be unavailable from 17:00 GMT Wednesday 20 November until 9:00 GMT Monday 25 November while we carry out important upgrades.

If you plan to update your membership, book an event or access APM Learning, APM Community or use other resources, please do this outside of these dates.

The 15 November Chartered Project Professional submission date is unaffected.

Thank you for your patience.

Why do we need agile project management?

Added to your CPD log

View or edit this activity in your CPD log.

Go to My CPD
Only APM members have access to CPD features Become a member Already added to CPD log

View or edit this activity in your CPD log.

Go to My CPD
Added to your Saved Content Go to my Saved Content
Gettyimages 669887538

Firstly, what is agile? The easiest way that I can explain to organisations and teams what being an agile organisation is, is through imagining a cat (stick with me)…

A cat leaps from a tall building, twists and turns, adapts to then land on its feet safely. An agile organisation is flexible and adapts to the ever-changing world, focusing on the user's needs and delivering customer-driven products, enabling continuous improvement and safe delivery.

Organisations that do not have an agile mindset, are much like the cat that freefalls, without flexing. This cat's future is sadly less fortunate, as are the organisations that follow. This is why it is so important for organisations to adopt an agile mindset if they want to thrive not just survive.

Customer centric

Agile organisations deliver value to their customers, incrementally; checking in on what’s still important to them and feeding back, adjusting, to the requirements their customers want and need.

By delivering value to our customers incrementally, we let them use the product sooner, give feedback and allow the project team to iterate upon it. Or in fact, customers can stick their hand up to say “Stop! We are happy with this! It fits our needs”. The value of this is immeasurable in itself, and can also save money, time and focuses the team’s creativity on the next value drive product for the customer.

Breaking down barriers

A core of agile is continuous improvement, both as a team; how teams together improve their processes, as well as the product. Continuous improvement requires continuous feedback, to one another, to our stakeholders and to our customers. It requires transparency and openness – values of agile and scrum – and it requires breaking down barriers. This is why I firmly believe and explain that agile is a mindset change, not an established, specific set of steps and instructions; but a way to look and approach a challenge.

For this to happen within organisations, there needs to be a learning culture; a culture that does not fear failure but embraces it. With fast failure, comes fast innovation, creativity and a safe experimental environment. To innovate and be ahead of the game, this environment is essential!

Embracing change

Responding to change over following a plan is another of the agile values. In today's world, if we don’t respond to change, adapt to a different plan and use complicated change processes that take weeks or months to agree and redesign, then we will fall behind.

Agile organisations embrace change, plan daily to progress and plan weekly to be able to have faster feedback loops from customers to pivot and adapt.

How do we build an agile mindset and culture?

It’s much easier to say than to do because changing a culture can take years.

  • Start an agile approach to change,
  • Do it in bite sized chunks
  • Experiment with different teams
  • Ask for feedback, be open and actively listen
  • Carry those energised with you
  • Nurture those who need more support.

Use the agile values as a guide:

Individuals and interactions over processes and tools
Communicate clearly, honestly and frequently.

Working product over comprehensive documentation
Get your product out there, to a good enough standard, it doesn’t have to be perfect. The value is in the feedback of the users.

Customer collaboration over contract negotiation
Be value driven, open to change and draft contracts based on that, over time and budget. Be flexible.

Responding to change over following a plan
Talk to your customers, and be flexible to change to deliver what they want, not necessarily what the initial idea was, as the beginning we know the least of what we want.

Summary

We need agile project management because it helps us focus on what matters. Becoming more agile through organisations and team’s brings flexibility to change and allows us to deliver value often with continuous feedback. The goal is not to ‘be agile’ the goal is to improve. With an incremental and iterative approach, we increase predictability and control risk.

A deep understanding of this lens as a way to see the world is vital so that you can continually incorporate and embody knowledge to ensure enduring performance and successful delivery.

Value what enables you to evolve to thrive (not just survive). Staying still is going backwards. Becoming agile isn’t a nice to have, it’s vital for the future.

You may also be interested in:

1 comments

Join the conversation!

Log in to post a comment, or create an account if you don't have one already.

  1. John Ellams
    John Ellams 17 January 2023, 04:24 PM

    Any downsides to this approach? What should we be looking out for in terms of what might go wrong (Murphy's Law!)?

  2. Helen Garcia
    Helen Garcia 18 January 2023, 10:43 AM

    Thanks John, and that’s a yes! Some that come to mind from my experience are… - Organisations that force a change, this cause issues as change is hard from many levels - expectation of a transformation is immediate, becoming an organisation that is flexible to change and that is a continuous learning organisation takes time. Moving into an agile mindset of delivery is often miscommunicated as “fast”. It can be, but in order to do this it’s important to slow down to speed up. - believing that agile is a methodology, when it’s a mindset. I refer often to my cat analogy, falling from a tall building, twist/turns lands safely. A cat doesn’t have instructions on how to do that, it’s taught and innate. To become more agile there are frameworks to support such as scrum/kanban, others… and to have a good understanding it’s important to value this. I’ll look to write another article and the down sides as it’s important to highlight for sure. Thanks for your comment.

  3. Adrian Pyne
    Adrian Pyne 20 June 2023, 11:12 AM

    Agility, unlike most other approaches in the project profession, is specifically predicated on certain behaviours. Notably, collaboration, delegation, empowerment etc. What this means is that for agility to be successful it definitely requires an organisation culture that supports agility. Central, very hierarchical organisations kill agility. Be aware that agility, based on the Agile Manifesto is a wholistic approach. Incremental delivery does not define agility, all 4 values and all 12 principles do. And a word of caution, 'incremental' and 'iteration' are not even mentioned in the agile manifesto. Alas APM's description of agile project management is quite wrong. It makes NO sense for a project management approach to be limited to projects ONLY with an iterative life-cycle. Project management is about a great deal more than just a life-cycle, project management agility encompasses ALL aspects of PM. If interested see my LinkedIn newsletter: Agile Beyond IT.