Agile Project Management

Agile Project Management (APM) is an iterative approach to planning and guiding project processes, that breaks it down into smaller cycles called sprints, or iterations.

Just as in Agile Software Development, an Agile project is completed in small sections. In Agile Software Development, for instance, an iteration refers to a single development cycle. Each section or iteration is reviewed and critiqued by the project team, which should include representatives of the project's various stakeholders. Insights gained from the critique of an iteration are used to determine what the next step should be in the project.

The main benefit of getting started with Agile Project Management is its ability to respond to issues as they arise throughout the course of the project. Making a necessary change to a project at the right time can save resources, and ultimately help deliver a successful project on time and within budget.

What is APM?

Agile project methodology breaks down projects into small pieces-- that are completed in work sessions that run from the initial design phase, to testing and quality assurance (QA). These sessions are often called sprints, the term for iteration used in one specific and popular Agile development method known as Scrum.

Sprints are generally short, running over days or weeks; they're typically two to four weeks long.

The Agile methodology enables teams to release segments as they're completed. This continuous release schedule allows for teams to demonstrate that these segments are successful and, if not, to fix flaws quickly. The belief is that this helps reduce the chance of large-scale failures, because there is continuous improvement throughout the project lifecycle.

How APM works

Agile teams build rapid feedback, continuous adaptation and QA best practices into their iterations.

They adopt practices such as continuous deployment (CD) and continuous integration (CI), using technology that automates steps to speed up the release and use of products.

Additionally, Agile Project Management calls for teams to continuously evaluate time and cost as they move through their work. They use velocity, burndown and burnup charts to measure their work, instead of Gantt charts and project milestones to track progress.

Agile Project Management does not require the presence or participation of a project manager. Although a project manager is essential for success under the traditional project-delivery methodologies, such as the waterfall model (where the position manages the budget, personnel, project scope, quality, requirements and other key elements), the project manager's role under APM is distributed among team members.

Learn how an Agile project can effect an entire business.

For instance, project goals are set by the product owner, while team members divvy up scheduling, progress reporting and quality tasks. Certain Agile approaches add other layers of management-- the Scrum approach, for example, calls for a scrum master who helps set priorities and guides the project through to completion.

However, project managers can still be used in Agile Project Management. Many organizations still use them for Agile projects -- particularly larger, more complex ones -- but the organizations generally place these project managers in more of a coordinator role, with the product owner taking responsibility for the project's overall completion.

Given the shift in work from project managers to Agile teams, Agile Project Management demands that team members know how to work in this new framework. They must be able to collaborate with each other, as well as with users. They must to be able to communicate well to keep projects on track. And they should feel comfortable taking appropriate actions at the right times, in order to keep pace with delivery schedules.

History of APM

The 21st century saw a rapid rise in use of the Agile Project Management methodology, particularly for software development projects and other IT initiatives.

However, the concept of continuous development dates back to the mid-20th century-- and has taken various forms, championed by different leaders over the decades. For example, there was James Martin's Rapid Iterative Production Prototyping (RIPP), an approach that served as the premise for the 1991 book Rapid Application Development and the approach of the same name, RAD.

A specific Agile Project Management framework that has evolved in more recent years is Scrum. This methodology features a product owner who works with a development team to create a product backlog, a prioritized list of the features, functionalities and fixes required to deliver a successful software system. The team then delivers the pieces in rapid increments.

Agile processes
A survey depicts commonly used Agile processes.

Additional Agile frameworks include Lean, kanban and Extreme Programming (XP).

APM vs. waterfall

Agile Project Management was, and remains, a counter to the waterfall methodology. The waterfall methodology features a strict sequential approach to projects, where initiatives start with gathering all requirements before the work begins, scoping out the resources needed, establishing budgets and timelines, performing the actual work, testing and then delivering the project as a whole when all the work is completed.

In response to what were recognized problems in that approach, 17 software developers in 2001 published the Agile Manifesto outlining 12 principles of Agile Software Development. The principles include to "welcome changing requirements, even late in the development" and "deliver working software frequently."

These principles continue to guide Agile Project Management even today.

Pros and cons

Advocates for Agile Project Management say the methodology delivers numerous benefits. Those include the rapid deployment of solutions, more efficient use of resources, greater flexibility and adaptability to changing needs, more rapid detection of problems -- and thus quicker fixes -- and increased collaboration with users and, therefore, products that better meet user needs.

There are also potential drawbacks, however, including a tendency for projects to go off track, a lack of documentation and less predictable outcomes.

Because Agile management relies on the ability to make decisions quickly, it is not suitable for organizations that tend to analyze issues for longer periods of time before taking action, or for those that take decisions to a committee.

This was last updated in August 2020

Continue Reading About Agile Project Management

Dig Deeper on IT project management and portfolio management

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

How do you handle the project manager role during an Agile project?
You eliminate it. Agile Project Management is an oxymoron.
You sound like a developer. :)
Agile software development methodology is a process for developing software using agile
As a project manager of 15 years on physical assets I find it hard to rationalize using Agile is it runs counter to absolutely everything I know about managing a project to be delivered on time and within budget. 
As a client of Dev Teams that use Agile all I hear when I ask for an estimate is "we dont set scope or schedule, and therefore assume you have an open ended check book"
If I go through the effort setting a clear set of functionality requirements - why can't you give me an estimate and schedule?!! At least based on fixed scope, and understanding that if I change scope I increase cost and schedule.
I understand why Dev teams like it - there's no accountability at all. However as a client with a budget - it sucks.
First of all, scope is NEVER fixed. If it were, everyone would be happy using waterfall and project managers. Scope in software development is constantly changing. 
Secondly, we aren't building homes or buildings, we aren't even "building software". We are creating software. That means it is different every time.  I can't tell you how many lines of code I need or how long it will take me to build you your widget since i have never built your widget before. So any estimate I give you will be nothing more than a SWAG. But you will insist you need it and I will spend days or weeks coming up with some bogus estimate that won't matter in three months anyway because the scope will change. And since we aren't using agile techniques to continuously test and integrate our software, all the estimates will become useless when it comes time to integrate everything and nothing works as expected. (If only we had spent three more months on design. I am sure we would have thought of everything...)
Personally I think the team’s fear in initial thread scenario is to providing an accurate eatimate on the unknown work in the future to get to end product/ release. I suggest the conversation could be what is the unknown and how much work you think you would need to do ( in time , resource etc) . If they say I don’t know. Then the next question could be when can we have a better understanding of the size of the work. Try to get get them to get to a committed plan to gain the knowledge to estimate the work . The dev team also shall know that it is okay give an accurate the estimation to begin with and provide more accurate one as you go. On the other hand you know the time line to launch and you know what features can be done if any and what are the list in product backlog are unknown . If I were you I would propose a 1-2 sprints to be prototyping sprints to learn the unknown to the point to estimate Hope this helps Cheers , Gee Weiden
This is why I 100% believe in Waterfall/Agile.  Overall, you have to have a roadmap.  "Where do we want to go with this?"  Then your Agile Sprints get you there.  The sprints contain, both, the original roadmap and the constant changes in scope.  That is what a PM does, in my opinion.  I can't develop software, but I can report and keep us on track so that your developers can stay heads-down and produce.
fully agree, the 2 methodologies can complement each other. I prefer the hybrid as a PM/scrum master I still need to provide accurate reporting to my business stakeholders on progress and delivery.
My organization is already working in Agile by using Scrum. Now we want to start PMO merged with Agile, how can we implement it successfully?
You use the PMO best practices/principles to define the big picture.  Once you reach WBS level, you start using Agile methodology
Agile is a tool that has been widely adapted well by software organization. Many hardware engineering , operations and other business functions shall take advantage of this tool. I would love to talk more about these topics further. Cheers, Gee Weiden
Not if you keep the iterations short.
Great article, thank you. I thought that some readers might be interested in developing the knowledge about agile project management, for example learn the difference between good and bad agile project management. I found an article about it, there you go:
Any project, no matter the style or kind of product to be delivered MUST HAVE someone to be accountable as main responsible for the final delivery.
You can call it Project Manager or Agile Coach or Scrum Master or Product Owner. Being a PM does not force this role to excecute the PMI body of knowledge as the Bible. In modern days, where humans are trying to find "the best way" to deliver a project, you need a true Architect Leader who will know how to combine different methodologies inthe the proper one for that especific project his being addressed.

Always remember: There are not two Projects the same. Even, lessons learned on Project "A" will prove useless on Project "B". Even less you will have the big winning methodology that works like "One size fits all" on every development.

Great article, for any readers who may be interested in developing their knowledge and trying out an efficient, innovative way to project manage and increase productivity I would recommend The site provides an online scrum board service and option to try it out for free
Thanks for the tips! 
I was wondering if there's any other softwares that you would recommend using?
Currently using Quire, a free project management software. Any other choices to look into?
Thanks for the excellent article, just to add an extra Agile portfolio into the mix, there is also now the Half Double Institute