7 Agile Project Management

Agile values and principles

Agile project management is an adaptive way to organize work when needs, solutions, or priorities may change as a project progresses. Rather than defining every detail at the beginning and delivering only at the end, a team plans in short horizons, produces usable results in increments, and uses feedback to decide what to do next. Agile is a set of values and principles, not one single method.

What the agile values prioritize

The Agile Manifesto expresses four value preferences:

• Individuals and interactions over processes and tools.

• Working software over comprehensive documentation.

• Customer collaboration over contract negotiation.

• Responding to change over following a plan.

These preferences do not mean that tools, documentation, contracts, or plans are unimportant. When priorities conflict, agile favors collaboration, usable results, and adapting to what is learned. Supporting principles include delivering value frequently, welcoming useful changes, maintaining a sustainable pace, building quality into the work, and regularly reflecting on how to improve.

Planning and delivering in increments

Agile planning takes place at several levels. A team may set a broad product goal, order a list of potential work, select a near-term objective, and adjust its detailed plan as it learns. The plan is not abandoned; it is updated using evidence from completed work and stakeholder feedback.

Incremental delivery divides a product or service into small, valuable parts and completes them in sequence. Each increment should be usable and meet agreed quality standards. Iteration is the repeated cycle of planning, doing work, reviewing the result, and adapting. In Scrum, this cycle takes place in a time-boxed Sprint. At its review, the team and stakeholders inspect what was produced and consider what should come next.

For example, a team creating an appointment-booking service might first deliver a basic way to find available times, then add booking confirmation, and later add reminders. After seeing how people use the first version, the team can reprioritize later work. Feedback can therefore inform decisions before the entire service is finished.

Practices for transparency and learning

Several practices help teams plan and learn as work progresses:

• A prioritized backlog: a visible, ordered list of possible work, refined as the team learns more.

• Small work items: break large requests into pieces that can be completed and checked within a short planning horizon.

• Frequent review: demonstrate completed work and collect feedback from customers or stakeholders.

• Retrospectives: examine how the team worked and agree on practical improvements.

• A shared definition of done: establish clear quality criteria that work must satisfy before it is considered complete.

These practices support transparency and adaptation. In Scrum, the Product Backlog, Sprint Backlog, and Increment have associated commitments that help make goals, work, and quality visible.

Scrum accountabilities and team responsibilities

Roles differ among agile methods. In Scrum, the Scrum Team has three accountabilities:

• Product Owner: maximizes product value and orders the Product Backlog. This role connects priorities to product goals and stakeholder needs.

• Developers: create a usable Increment, plan and adapt their work, and maintain quality. “Developers” means the people doing the work, not only software programmers.

• Scrum Master: helps establish Scrum, supports the team's effectiveness, and helps address impediments to progress.

The Scrum Team is self-managing and cross-functional. Together, its members have the skills needed to produce value, and they decide how to organize the work. Sponsors, customers, users, specialists, or governance groups may provide input and constraints. They are important contributors, but they are not automatically Scrum Team roles.

Other agile approaches may use different role names or prescribe no formal roles. Teams should distinguish responsibilities that must be covered—such as prioritizing work, producing results, and enabling improvement—from the particular job titles used by a method.

Choosing an approach to delivery

No single life cycle is best for every project. Select an approach by considering how uncertain the requirements and solution are, how often useful feedback can be obtained, how work arrives, and what constraints govern delivery. Project characteristics and organizational needs should guide the choice, and approaches can be combined.

• Iterative, incremental agile delivery may fit when priorities or requirements are likely to evolve, stakeholders can give feedback, and useful portions of the result can be delivered and evaluated along the way.

• A flow-based approach such as Kanban may fit when work arrives continuously or unpredictably. Kanban makes the workflow visible, actively manages work in progress, and uses flow information to improve delivery.

• A predictive approach may fit when the scope and solution are well understood and major constraints require substantial planning up front. Predictive planning can also suit parts of a project even when other parts are uncertain.

• A hybrid approach may fit when some work benefits from fixed milestones, approvals, or predictable sequencing while other work benefits from frequent feedback and adaptation. Agile and predictive practices can be combined rather than treated as all-or-nothing alternatives.

For example, replacing a well-understood piece of equipment may call for a detailed procurement and installation plan. If the project also includes a new customer-facing app whose requirements need user testing, that component could be delivered iteratively. The approach should fit the different kinds of work and the project's constraints.

Putting the ideas together

Agile prioritizes collaboration, usable results, and response to change while still using plans, documentation, and quality standards where they add value. Teams plan in manageable horizons, deliver and inspect increments, and adapt based on feedback. Roles depend on the method: Scrum specifies a Product Owner, Developers, and Scrum Master. Choose agile, predictive, flow-based, or hybrid delivery to fit the work's uncertainty, feedback opportunities, workflow, and constraints.