4 Choosing an Approach for a Project

Understand the approaches

No project-management approach is best for every project. Choose an approach that fits the work, constraints, and people, and revisit that choice when conditions change. All approaches require planning, but they differ in how much planning happens up front and how often it is revised.

A Predictive approach emphasizes defining and planning work early. An Adaptive approach, often called agile, uses short cycles, feedback, and adjustment. A Hybrid approach combines practices from both.

Assess the project

Assess the project with evidence rather than choosing a familiar method by default. Consider each factor below, including where different parts of the project may have different needs.

Uncertainty and requirements

Ask whether the solution, technology, and desired outcome are understood. Stable, proven work favors predictive planning; high uncertainty or rapid change favors adaptive experiments and frequent feedback. If uncertainty is extreme, first reduce it with a prototype or feasibility test rather than assuming a framework alone will solve it.

Requirements that can be specified and approved early suit a predictive baseline. Requirements likely to evolve suit adaptive prioritization and incremental delivery. A project may include both stable requirements for one component and uncertain requirements for another.

Stakeholders and constraints

Identify who approves scope, who will use the result, and how often they can provide feedback. Adaptive work depends on timely stakeholder access. If feedback is infrequent or decisions require formal approval, plan explicit review and decision points. Agree on measures of success before delivery begins.

Consider constraints involving safety, privacy, security, quality, procurement, and legal or regulatory obligations. Identify required approvals, evidence, and audit records. These constraints do not automatically rule out adaptive work: compliance checks and approvals can be built into each iteration while maintaining required traceability and release controls.

Dependencies and team readiness

Map external suppliers, other teams, fixed interfaces, and tasks that must occur in sequence. Many tightly coupled dependencies can require integrated planning, coordination, and milestones. Independent work may be delivered iteratively while shared interfaces and integration dates are coordinated.

Check whether the team has the skills, availability, authority for day-to-day decisions, tools, and access to users or specialists needed for the approach. If readiness is limited, provide support or training, clarify decision rights, or choose a more structured transition. Do not label a team agile without enabling the collaboration and feedback that approach needs.

Choose a starting approach

Use the assessment to choose a starting point, not a permanent label.

• Predictive: Favor this when scope and solution are well understood, change is limited or costly, and sequencing, formal approvals, or fixed commitments dominate.

• Adaptive/agile: Favor this when requirements or solutions are uncertain, frequent stakeholder feedback is available, and useful increments can be delivered and evaluated.

• Hybrid: Favor this when different parts of the work have different needs. Define which practices apply to each part and how the parts integrate.

Apply the choice to a project

A company is building a new customer portal. Hosting infrastructure and privacy approvals have defined requirements and must pass formal reviews, while the user-facing features are not yet clear. A hybrid approach could plan infrastructure, security evidence, and approval gates predictively, while developing portal features in short increments with user feedback. Shared integration dates and dependency owners connect the two streams.

Document and revisit the decision

Document the chosen approach, key assumptions, trade-offs, review cadence, and conditions that would trigger a change. Reassess at major milestones or when requirements, risks, regulations, dependencies, or team capacity shift.

Tailoring is a reasoned fit to the project, not a contest between methods. Match stable, tightly controlled work with predictive planning, use adaptive delivery where learning and change are central, and combine practices when the project contains both. Explain the choice, preserve necessary controls, and review it as conditions evolve.