Methodologies · Letter A

Agile Project Management

An iterative, incremental approach to delivering value through self-organising teams and short feedback loops.

By Dr. Hassan Khames Eliwa, PhD · Updated 2025-05-02

Definition

Agile Project Management is a delivery philosophy that organises work around short, time-boxed iterations, continuous stakeholder feedback, and adaptive planning rather than a single up-front plan. It originated in software but is now applied to product development, R&D, marketing, and increasingly to engineering design phases on capital projects.

History

The Manifesto for Agile Software Development was published in 2001 by 17 practitioners who codified principles that had been emerging through Scrum (Schwaber & Sutherland, 1995), Extreme Programming (Beck, 1999), Crystal, and DSDM. PMI later integrated agile into the Agile Practice Guide (2017) and the PMBOK® Guide 7th edition shifted entirely from process groups to performance domains to accommodate hybrid delivery.

Principles

  • Deliver working increments early and often.
  • Welcome changing requirements, even late in development.
  • Self-organising, cross-functional teams.
  • Face-to-face communication where possible; written artefacts where necessary.
  • Sustainable pace — no heroics, no death marches.
  • Continuous reflection and adaptation through retrospectives.

Applications

Agile is the default approach for software products, mobile apps, and data platforms. In engineering, agile patterns appear in design sprints during FEED, in set-based concurrent engineering for product development, and in last-planner short-interval planning on construction sites. Hybrid models (agile design, predictive execution) dominate complex programs that combine discovery work with predictable construction.

Real Example

A digital-twin team supporting a metro construction program ran two-week sprints to deliver visualisation features. The product backlog was prioritised every sprint by the project director and the BIM lead; releases were demoed to site supervisors, and feedback was incorporated into the next sprint. Cycle time from idea to deployed feature dropped from 11 weeks to 18 days.

Best Practices

  • Define a clear product vision and a measurable definition of done.
  • Keep teams stable, small (5–9 people), and dedicated.
  • Use a visible board (physical or digital) and limit work-in-progress.
  • Measure flow (lead time, throughput) rather than utilisation.
  • Pair every sprint with a retrospective that produces at least one improvement action.

Common Mistakes

  • "Agile theatre" — daily stand-ups and Jira tickets without genuine empowerment of the team.
  • Forcing agile rituals onto highly regulated, fixed-scope work.
  • Treating velocity as a productivity KPI.
  • Skipping retrospectives once delivery pressure rises.

References

  • Beck, K. et al., Manifesto for Agile Software Development, 2001.
  • PMI, Agile Practice Guide, 2017.
  • Schwaber, K., Sutherland, J., The Scrum Guide, 2020.

Frequently Asked Questions

  • Can agile work on construction projects?
    Pure Scrum rarely fits field construction, but agile principles — short cycles, transparent boards, retrospectives — translate well to design phases and to last-planner short-interval planning on site.
  • Agile vs Waterfall — which is better?
    Neither. Predictive approaches outperform when scope is well known and change is expensive. Adaptive approaches outperform when learning is required. Most modern programs are hybrid.
  • Which calculators on PMMilestone.org apply to Agile Project Management?
    For Agile Project Management, the most relevant tools on the flagship platform are the Schedule Health Checker (CPM logic) and EVM Calculator. They reproduce the formulas referenced in this entry against your own project data.
  • What is a common misconception about Agile Project Management?
    That Agile, PMBOK, PRINCE2 and Lean are alternatives. On large capital programmes they coexist — PMBOK at the programme layer, Lean / Last Planner System at the construction front, and Agile for the digital deliverables. The methodology is chosen per layer.
  • Which related encyclopedia entries should I read alongside Agile Project Management?
    Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
  • How does Dr. Hassan Eliwa's research treat Agile Project Management?
    Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Agile Project Management is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
  • How is Agile Project Management defined on PMMilestone Research & Insights?
    An iterative, incremental approach to delivering value through self-organising teams and short feedback loops. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Related Entries

Further reading on PMMilestone.org

Curated companion resources hosted on the flagship platform,PMMilestone.org.

Related Encyclopedia Entries
Related Research Articles
Related Case Studies
Related Tools on PMMilestone.org