Agile project management is an approach to planning and executing work through short feedback cycles, incremental delivery and continuous adjustment. Instead of assuming that every requirement and activity can be defined accurately at the beginning of a project, Agile allows teams to learn during execution and adapt plans when new information becomes available.
The approach grew largely from software development, but the underlying concepts can also apply to engineering, product development and other environments where uncertainty makes excessive long-range detail unreliable.
What does Agile mean?
The Manifesto for Agile Software Development emphasizes individuals and interactions, working products, customer collaboration and responding to change. Its accompanying principles emphasize frequent delivery, feedback and adaptation.
Agile is broader than any one framework. Scrum and Kanban can be used to implement Agile ideas, but Agile itself is not a prescribed schedule template or specific set of ceremonies.
How Agile planning works
Agile planning normally occurs at several horizons. Longer-range planning establishes product objectives, releases and major dependencies. Near-term planning becomes progressively more detailed as the team gains information.
This resembles rolling-wave planning. Work that is sufficiently understood can be planned at a detailed level while future work remains at a higher level until responsible detail can be developed.
Agile does not mean no schedule
Large programs still have contractual dates, interfaces, hardware dependencies, customer milestones, test events and funding constraints.
The important distinction is that a detailed Agile backlog should not automatically become a program-level schedule. A well-designed Integrated Master Schedule can represent Agile releases, interfaces and program milestones without reproducing every user story as a schedule activity.
Agile on DoD programs
The Defense Acquisition University provides Agile acquisition resources for defense programs, including guidance on Agile concepts, roles and terminology.
For program planners, this creates an integration challenge rather than a simple choice between Agile and traditional planning. Software teams may execute iteratively while the larger program still requires an IMS, contractual reporting, performance measurement and integration with engineering, procurement and test organizations.
Agile planning at the program level
The program planner should focus on information that crosses organizational boundaries. This commonly includes releases, interfaces, required environments, integration events, qualification activities and contractual milestones.
The Agile team can manage detailed execution within its delivery system while program controls maintains the integrated view required to understand overall execution.
Agile is adaptive planning, not an absence of control
Good Agile implementation requires disciplined prioritization, transparent dependencies, clear completion criteria and frequent measurement of actual results.
The next distinction to understand is how adaptive planning differs from predictive planning. See Agile vs Waterfall Project Management.