2 Adaptive and Agile Project Management
Learn how adaptive, agile, predictive, and hybrid approaches fit different project conditions, and how teams plan, deliver, review, and improve work.
Project approaches and life cycles
A describes how work is organized and delivered. A plans much of the work in advance, while an expects learning and change during delivery.
is a family of values and principles that supports adaptive work, not a single prescribed process. It emphasizes collaboration, frequent delivery of value, and response to change while still recognizing the value of plans, tools, and documentation.
Adaptive approaches are especially useful when requirements are uncertain, stakeholders can give feedback regularly, and work can be delivered in small increments. More upfront planning may be appropriate when requirements are stable or work has fixed dependencies, regulatory controls, or major one-time construction. These are not absolute rules: a project can combine approaches to fit its context.
revisits and improves a solution over cycles. adds usable pieces over time. Many teams do both: they deliver a small working increment, learn from its use, and refine what comes next.
Principles for responding to change
When changes or obstacles arise, adaptive teams prioritize valuable outcomes and early delivery over completing every originally proposed feature. They welcome useful new information even when it changes the plan, collaborate with users and stakeholders throughout the work, and make progress visible through completed, usable work rather than activity or documents.
Teams also reflect on results and working practices, then adjust. Maintaining quality and a sustainable pace matters; agility is not a reason to skip testing or continually overload a team.
A change request is neither automatically accepted nor automatically rejected. The team and decision-makers consider its value, urgency, risks, dependencies, and effect on the current goal and capacity. They may reorder planned work, defer lower-value items, or decline the change if it does not justify the trade-off.
Scrum accountabilities and shared responsibility
Roles depend on the method in use. In Scrum, the Scrum Team consists of a , a , and .
The is accountable for maximizing product value and managing the , including making its ordering clear. The helps establish Scrum, supports team effectiveness, and helps address impediments. create a usable increment each , plan their work, and adapt their approach toward the Goal.
The team is cross-functional and self-managing: members collectively decide how to do the work, while the clarifies priorities. A project manager may also be involved in a broader organization or hybrid project, but that title is not one of Scrum's three accountabilities.
Planning, feedback, and Scrum events
Adaptive planning happens at multiple horizons rather than only at the start of a project:
Set direction: Clarify the desired outcome, users, constraints, and measures of success.
Maintain an ordered backlog: Record potential work as features, tasks, or user needs, and refine items as understanding improves.
Plan a short cycle: Select work that fits the team's capacity and define a clear near-term goal. Treat the plan as a forecast, not a guarantee that every detail is already known.
Build and check quality: Coordinate frequently, surface blockers, and test work as it is created.
Review the increment: Demonstrate completed work to stakeholders and gather feedback about whether it solves the right problem.
Improve the process: Reflect on collaboration, flow, quality, and obstacles, then choose practical adjustments for the next cycle.
In Scrum, the , Planning, Daily Scrum, Review, and Retrospective support these activities. The events provide regular opportunities for transparency, inspection, and adaptation. Backlog refinement is ongoing work, not a formal Scrum event.
Feedback is useful only when it can influence decisions. For example, a team building an appointment-booking service may learn in a review that users need to reschedule appointments more than they need a new visual theme. The can reorder the so rescheduling is considered sooner, while the team assesses dependencies and capacity.
Practices for delivery and continuous improvement
Teams use practices that help them deliver, inspect, and improve work:
Small increments: Deliver and validate usable pieces of a product rather than waiting for a large final release.
Visualize work: Use a board or another shared display to show work status, blockers, and flow.
Limit : Avoid starting more work than the team can finish; complete items before pulling in new ones.
Frequent testing and integration: Find defects and integration issues early, when they are generally easier to address.
Regular stakeholder feedback: Check both the product and assumptions about user needs.
Retrospectives and experiments: Identify a specific improvement, try it, and inspect whether it helped.
emphasizes visualizing work, limiting work in progress, managing flow, making policies explicit, and using feedback loops for collaborative improvement. It can be applied to an existing workflow and does not require fixed-length iterations.
Choosing an approach for the project
Choose an approach in light of requirements, feedback opportunities, dependencies, and constraints; a project need not use one method uniformly in every part.
Uncertain product requirements: A team creating a new customer app whose users are unsure which features they need can use an , short delivery cycles, frequent demonstrations, and a reordered backlog. Timely user feedback is important; without it, iteration may produce little learning.
Stable, highly dependent work: A facility upgrade with approved designs, procurement lead times, and a fixed inspection sequence calls for predictive planning of major dependencies and approvals. If the same project includes a software dashboard with uncertain user needs, that component can be developed iteratively and its milestones coordinated with the larger plan.
Hybrid delivery: When a project has a fixed launch date and security review but an evolving customer-facing feature, external milestones, budget controls, and required security checks can be set predictively. The feature can be developed and refined in short cycles with stakeholder review. Make integration points and decision authority explicit.
Before choosing or adjusting an approach, ask:
How certain are the requirements and solution?
How quickly can users or stakeholders provide meaningful feedback?
Can the work be divided into small, valuable increments?
Which constraints, such as safety, regulation, procurement, or fixed deadlines, need upfront coordination?
What planning cadence and controls will help the team learn without losing visibility or accountability?
Choose an approach that fits the uncertainty and constraints, then reassess it when evidence changes. Predictive, adaptive, or hybrid choices should follow project conditions rather than a preference for a label.