A Beginner’s Guide to Agile Project Management

As the name suggests, Agile project management promotes an adaptable approach to projects. Dating back to 2001, it originated in the digital industry with software development projects but is now increasingly applied across a range of sectors, with organisations preferring its flexible and client-involved approach.

Agile began life when a group of seventeen people convened in Utah, USA to discuss the pitfalls of the traditional project management approaches when they are applied to the software industry. The meeting resulted in the ‘Agile Manifesto’, setting out the core values of the Agile project management style which showed a preference for:
“Individuals and interactions over processes and toolsr
Working software over comprehensive documentationr
Customer collaboration over contract negotiationr
Responding to change over following a plan”

In practical terms, what are the defining features of Agile project management?

In a project setting, an Agile approach typically shows the following key working preferences:
• Daily contact between project managers and delivery staff, with a preference for face-to-face discussion over email or telephone
• A preference for shorter timescales, taking an incremental approach by delivering work to the client in stages
• Allowing for changing requirements organically, for the benefit of the client and final product
• Promoting a trusting, empowered environment conducive to high-quality work
• Client-side involvement – allowing for change requests throughout the process, instead of at the project test phase

What working frameworks are applied to the Agile methodology?

Whilst the Agile Manifesto set out the core values of the project management style, it did not necessarily define the ‘how’. It has been up to organisations to find working methods that are conducive with the Agile method.
‘Scrum’ is just one framework method applied to Agile, using a cross-functional team to take a collaborative approach to solutions and problem-solving. With the help of a ‘Scrum Master’ who ensures the Scrum framework is maintained, and a ‘Product Owner’ who champions the high-level client requirements and maintains project oversight, the aim is to take a people-focussed, whole team approach.

Scrum organises project deliverables into ‘sprints’ which have a defined and short timescale; each sprint will cover a key element of the project from start to finish, and on completion the key stakeholders will review and then plan the next stages. This is where the adaptable Agile approach is evident – the project’s direction is determined throughout the process, allowing for change as required for the benefit of all.

Reflecting the preference for face-to-face contact between team members, a meeting known as the ‘daily scrum’ will be held each and every working day, with a short timescale of usually no more than 15 minutes. This is a chance for team members to quickly provide an update, and agree on the best way forward for the day ahead.

How do I learn more?

There are many training courses, books and online resources such as a project management blog available to get you started with the Agile approach. Alternatively, you could talk with your employer about potential plans to adopt an Agile project management technique.