Skip to content
Added to your Saved Content Go to my Saved Content 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
Tunnel 620 X 620

What is agile project management?

Agile project management is an iterative approach to delivering a project throughout its life cycle.

Iterative or agile life cycles are composed of several iterations or incremental steps towards the completion of a project. Iterative approaches are frequently used in software development projects to promote velocity and adaptability since the benefit of iteration is that you can adjust as you go along rather than following a linear path.

One of the aims of an agile or iterative approach is to release benefits throughout the process rather than only at the end. At the core, agile projects should exhibit central values and behaviours of trust, flexibility, empowerment and collaboration.

Traditional project management vs agile project management

What is agile project management? Hybrid. Linear or Waterfall approaches. Iterative or Agile Approaches.

What are the principles of an agile way of working?

The agile management philosophy concentrates on empowered people and their interactions, and early and constant delivery of value into an enterprise. 

Iterative or agile project management focuses on delivering maximum value against business priorities in the time and budget allowed, especially when the drive to deliver is greater than the risk. Some agile principles include:

  • The project breaks a requirement into smaller pieces, which are then prioritised by the team in terms of importance.
  • The agile project promotes collaborative working, especially with the customer. 
  • The agile project reflects, learns and adjusts at regular intervals to ensure that the customer is always satisfied and is provided with outcomes that result in benefits.
  • Agile methods integrate planning with execution, allowing an organisation to create a working mindset that helps a team respond effectively to changing requirements.
More on agile principles

Becoming agile

The move to becoming an agile organisation brings change. It impacts on the traditional culture and introduces new ways of working on projects – so not everyone will be convinced. What does it take to successfully introduce that change?

This is a member only resource. Not a member? Join today

Read blog (🔒)

How agile is agile?

In this age of pandemic, how agile is agile project management? With the key agile principle of informal collaboration and communication seemingly hindered by remote working, is agile up to the challenges? Six months into APM’s major study of agile with the University of Southampton, themes are starting to emerge.

Read blog

Watch: The practical adoption of scaled agile

Interview with Sue Clarke

This APM Research Fund study builds on the APM North West Volunteer study on the practical adoption of agile methodologies which provided a review of approaches at a project level, this study aims to investigate the level of practical adoption of those programme and portfolio components addressed by scaled agile methodologies. 

The objective of the study was to understand the extent to which scaled agile tools, techniques and roles are practically in place in corporate portfolio, programme, project and development management methodologies, to determine the level of corporate commitment to exploiting scaled agile, e.g. pilot, full use, selective based on need, as well as drivers for selection or deselection of the framework based on the overheads.

Watch part 2

What are the benefits of agile working?

Agile approaches empower those involved; build accountability; encourage diversity of ideas; allowing the early release of benefits; and promotion of continuous improvement.

Agile helps build client and user engagement because changes are incremental and evolutionary rather than revolutionary: it can therefore be effective in supporting cultural change that is critical to the success of most transformation projects.

Agile allows decision ‘gremlins’ to be tested and rejected early: the tight feedback loops provide benefits in agile that are not as evident in waterfall.
Read more

What are the differences between an agile and waterfall approach?

These four aspects highlight the difference between agile and waterfall (or more traditional) approaches to project management:


Customer collaboration over contract negotiation


Individuals and interaction over process and tools


Responding to change over following a structured plan


Prototyping/working solutions over comprehensive documentation

Read more

What are agile techniques?

A project managers guide to agile or iterative techniques

There are various iterative or agile techniques that can suit any project method, they’re not limited to agile. You also don’t have to use them all; choose the ones that work for you, your team and the project.

This infographic is brought to you by the interactive APM Learning module.

Download guide

Agile project management glossary

Iterative or agile terminology can be confusing. We have compiled a list of the most common agile terminology you may come across, and their definitions:

  • Agile – a project management approach based on delivering requirements iteratively and incrementally throughout the life cycle.
  • Agile development – an umbrella term specifically for iterative software development methodologies. Popular methods include Scrum, Lean, DSDM and eXtreme Programming (XP).
  • Agile Manifesto – describes the four principles of agile development: 1. Individuals and interactions over processes and tools. 2. Working software over comprehensive documentation. 3. Customer collaboration over contract negotiation. 4. Responding to change over following a plan.
  • Backlog – prioritised work still to be completed (see Requirements).
  • Burn down chart – used to monitor progress; shows work still to complete (the Backlog) versus total time.
  • Cadence – the number of days or weeks in a Sprint or release; the length of the team’s development cycle. 
  • Ceremonies – meetings, often a daily planning meeting, that identify what has been done, what is to be done and the barriers to success.
  • DAD (disciplined agile delivery) – a process-decision framework.
  • Daily Scrum – stand-up team meeting. A plan, do, review daily session.
  • DevOps (development/operations) – bridges the gap between agile teams and operational delivery to production.
  • DSDM (dynamic systems development method) – agile development methodology, now changed to the ‘DSDM project management framework’.
  • Kanban – a method for managing work, with an emphasis on just-in-time delivery.
  • Kanban board – a work and workflow visualisation tool which summarises the status, progress, and issues related to the work.
  • Lean – a method of working focused on ‘eliminating waste’ by avoiding anything that does not produce value for the customer.
  • LeSS (large-scale Scrum) – agile development method.
  • RAD (rapid application development) – agile development method; enables developers to build solutions quickly by talking directly to end users to meet business requirement.
  • Requirements – are written as ‘stories’ that are collated into a prioritised list called the ‘Backlog’.
  • SAFe (scaled agile framework enterprise) – agile methodology used for software development.
  • Scaled agile – agile scaled up to large projects or programmes, for example by having multiple sub-projects, creating tranches of projects, etc.
  • Scrum – agile methodology commonly used in software development, where regular team meetings review progress of a single development phase (or Sprint).  
  • Scrum of scrums – a technique to operate Scrum at scale, for multiple teams working on the same product.
  • Scrum master – the person who oversees the development process and who makes sure everyone adheres to an agreed way of working.
  • Sprints – a short development phase within a larger project defined by available time (‘timeboxes’) and resources.
  • Sprint retrospective – a review of a Sprint providing lessons learned with the aim of promoting continuous improvement.
  • Stories – see Requirements.
  • Timeboxes – see Sprints.
  • Velocity – a measure of work completed during a single development phase or Sprint.
  • Waterfall – a sequential project management approach that seeks to capture detailed requirements upfront; the opposite to agile.
  • XP (eXtreme Programming) – agile development methodology used in software development; allows programmers to decide the scope of deliveries.

Related reading

Agile Card 2
What are the principles of agile working?

Four principles that highlight the difference between agile and waterfall

Learn more
Shutterstock 1172963929
What are agile methods and methodology?

Read more about the methods and principles of agile.

Learn more
Conversation 340X204
The five most expensive project agility mistakes

I really shouldn’t complain. After all, I have often made a good living from rectifying big project mistakes... Read more.

Read blog
Understanding Agile
Understanding agile in project management

The use of agile in project management remains relatively new and is evolving for many organisations.

View research
Agile Summt Report
Agile summit report

A panacea or placebo for project delivery?

Read report
Does Agile Work (1)
Does agile work?

This article looks at the benefits, or not, of applying an agile method of project management, as opposed to more traditional methods.

Download research
Can Agile Be Scaled (2)
Can agile be scaled?

A study to understand scaled agile tools, techniques and roles.

Download research
Practical Adoption Of Agile
Practical Adoption of Agile Methodologies

Agile needs more from a project manager in way of communication for risks, issues and stakeholder management, as speed of resolution is of the essence. By members of the APM North West branch.

Read more
Agile And Earned Value
Agile and Earned Value - White paper

This paper will discuss the EVM techniques which have been adopted to provide the benefits of traditional EVM in agile projects.

Read more
Directing Agile Change (1)

Directing Agile Change

Directing Agile Change is the first ‘how to’ agile guide published by APMIt seeks to recognise that agile is not limited to software development but can also be applied to many aspects of an organisation.

Buy from the bookshop
A Guide To Assurance Of Agile Delivery

A Guide to Assurance of Agile Delivery

This guide shows how undertaking traditional assurance reviews can be adapted and adopted to ensure assurance activity of agile projects is both effective and valuable.

Buy from the bookshop

You may also be interested in

Apm Learning V2 Card
APM Learning

The APM Learning portal is an online resource which provides members with access to digital guides, modules and other digital learning resources as part of the membership benefit.

Resources V2 Card
What is ...?

Browse our popular project management 'What is ...?' topics for definitions, quick insights, view related case studies, research, blogs and glossary.

Project V2 Card
Project Journal

Project – APM's official journal – is circulated quarterly for members only, and online for regularly updated news, blogs, opinions and insights for those in the project community.

Hub V2 Card
APM Community

The APM Community is our online community platform that connects our members faster and easier than ever before.