PMP Development Approaches: Predictive, Agile, and Hybrid
Introduction
Choosing a project development approach starts with the work. A warehouse safety system may need a coordinated installation and formal acceptance, while a driver app can benefit from testing small releases with users.
This lesson covers the assessment and delivery choices in Task 1 of the Process domain of the July 2026 PMP Examination Content Outline (ECO). Process accounts for 41% of exam coverage. PMI describes the exam mix as approximately 40% predictive and 60% adaptive/agile and hybrid combined, with approaches appearing across all domains. You will assess project needs, compare approaches, and recommend an execution strategy that fits the constraints.
Learning objectives
- Assess project needs, complexity and magnitude with structured criteria.
- Distinguish the life cycles and development approaches: predictive, iterative, incremental, agile and hybrid.
- Recommend the approach that fits the project and justify it.
- Identify critical information requirements, including sustainability and regulatory inputs.
- Recommend a project execution strategy (contracting, financing, resourcing).
- Tailor the approach and the artefacts to the project and to the organisation.
1. Assessing needs, complexity and magnitude
Before choosing how to work, understand what is being asked. Three lenses help.
Needs. What problem or opportunity does the project address, what benefits are expected, and what do the stakeholders consider success? Needs come from the business case, the charter, the sponsor, users and regulators. A need can be stable ("migrate 40 branch offices to a new telephone system") or emerging ("find out which features customers will actually pay for").
Complexity. Complexity comes from the number and interaction of elements, not just their size. Typical sources:
- Human behaviour: many stakeholders with conflicting interests, cultural differences, politics.
- System behaviour: dependencies between components, feedback and emergent effects.
- Ambiguity: unclear requirements, new technology, unknown solution.
- Technical uncertainty: unproven design, integration with legacy systems.
Magnitude. Size of the budget, number of people, duration, number of locations, level of risk and regulatory exposure.
Use a comparison table with the sponsor and the team. For each factor, record evidence and any constraint that rules out an option.
| Criterion | Points towards predictive | Points towards agile |
|---|---|---|
| Requirements | Well known and relatively stable | Unclear, evolving, discovered by feedback |
| Solution | Proven, low technical uncertainty | New or experimental |
| Change | Expensive, controlled | Expected and welcome |
| Customer access | Limited, formal sign-off | Available, can give frequent feedback |
| Evidence and approvals | Delivery depends on a sequence of formal reviews or a single approval | The team can build and review evidence alongside increments |
| Delivery value | One release at the end gives the value | Early partial releases give value |
| Team capacity | Specialists are available at defined stages | A cross-functional team is available to learn and deliver in short cycles |
| Governance | Scope and funding are committed at defined approvals | Decision-makers can review outcomes frequently and reorder work within agreed limits |
Use the comparison to make a recommendation. For example, an approval gate can coexist with short feedback cycles when the team produces evidence as it delivers.
Example: assessing two projects at the same company
Nordhaven Logistics has two projects. Project A replaces the fire-suppression system in a warehouse: fixed scope set by a safety regulator, a fixed budget of EUR 1.8 million, a contractor, a 7-month schedule, and no value until the system is certified. Project B builds a mobile app for drivers to report delays: the company is not sure which features drivers will use, the business wants to test in two depots, and early releases would already save time. Project A scores strongly "predictive": stable requirements, regulation, one release. Project B scores strongly "agile": uncertain requirements, frequent feedback from drivers, incremental value. Using one approach for both would hurt one of them.
2. Life cycles and approaches
The ECO groups recommendations into predictive, adaptive/agile, and hybrid. Iterative and incremental describe how teams refine or deliver the solution. A project can use both.
| Approach | How it works | Typical fit |
|---|---|---|
| Predictive (plan-driven) | The team plans a relatively stable scope and its schedule and cost early, then refines the plan and controls changes to approved baselines. | Stable requirements, regulated or contract-based work, construction, hardware, migrations |
| Iterative | The solution is built and refined through repeated cycles; scope is understood progressively. | Scope unclear, need feedback to improve a solution |
| Incremental | The solution is delivered in usable pieces; each increment adds capability. | Value can be released in stages |
| Adaptive / agile | The team plans and learns in short cycles or through continuous flow. Feedback informs which work to do next. | High uncertainty, frequent change, product development |
| Hybrid | A combination: for example, a predictive plan for the overall frame, agile delivery for part of the work, or agile execution within contracted stages. | Mixed constraints: fixed budget and date but uncertain scope; hardware plus software |
The agile mindset in brief
The Agile Manifesto emphasises collaboration, working software, and responding to what the team learns. Scrum is one framework a team can use. The Scrum Guide defines the accountabilities of the Product Owner, Scrum Master, and Developers, and identifies the Product Backlog, Sprint Backlog, and Increment as artefacts. Scrum teams inspect outcomes and adapt their plans in the Sprint.
Common hybrid delivery patterns
Hybrid choices are deliberate. Common patterns:
- Predictive frame, agile delivery. A fixed funding envelope, milestones and governance, while the product team works in sprints on a prioritised backlog.
- Different approaches for different parts. Hardware with a fixed lead time follows a predictive plan; software on top is built iteratively.
- Agile discovery, then predictive build. Prototypes and iterations define the requirement, then a stable build phase follows.
- Predictive first, agile after. Implementation of a solution in stages, followed by continuous improvement in a flow-based team.
Explain what each part contributes and how the teams coordinate their dependencies and approvals. The lesson on building an integrated project management plan shows how to check the resulting plan for mismatched dates, resources, and approvals.
3. Recommending an approach
The ECO uses the verb "recommend": the project manager analyses the options and recommends an approach. Confirm who can approve it under the organisation’s governance. A good recommendation:
- States the assessed needs, complexity and magnitude.
- Lists options and compares them against the criteria.
- Identifies risks of each option and how they would be handled.
- Considers organisational constraints: policies, contracts, regulators, skills, tools, culture.
- Includes a plan to tailor, with a way to review if conditions change.
Factors that can override an otherwise good fit include a contract that requires fixed scope, a regulator that requires a formal documented process, or a team with no agile experience. These do not make agile impossible, but they influence the form: for example, a buyer and supplier can agree on a fixed price for an increment or period while retaining an agreed way to order work. Read the contract before assuming scope is flexible.
Worked example: choosing an approach
Statement. Alder Insurance wants a customer self-service portal. The business has a firm launch date at the start of the next financial year (10 months) and a capped budget of EUR 2.4 million. Product managers have a list of 60 wishes but admit that only about 15 will matter to customers. The project must deliver specified data-protection controls and demonstrate them with documented evidence. Developers have two years of Scrum experience. The sponsor asks you for a recommendation.
Reasoning, step by step.
- Needs. The main need is a working portal at launch that customers use. Value arrives incrementally: a basic login and policy view already has value.
- Complexity. Scope is uncertain (15 of 60 wishes matter), integration with core systems is known, user behaviour is unknown. Medium-high ambiguity.
- Magnitude. EUR 2.4 million, 10 months, moderate team size.
- Constraints. Fixed date and cap on budget; data-protection controls need documented evidence.
- Options. (a) Baseline the feature set after upfront discovery, with scheduled validation and formal change approval. (b) Use adaptive delivery across the project, with frequent reviews of the budget, controls, and launch forecast. (c) Combine predictable funding and release gates with two-week Sprints for learning which features users need.
- Recommendation. Hybrid (c) fits this sponsor’s approval process. Protect required controls and decide which optional features fit within the date and budget. Include evidence relevant to each Increment in its Definition of Done and plan separate approvals where required. Track release forecasts and milestone readiness.
Why this combination fits. A detailed scope baseline would be costly to revise while user needs are uncertain. An adaptive approach can also manage budget and compliance. The proposed hybrid makes the sponsor’s formal decision points explicit and lets the team test optional features early.
4. Critical information requirements, including sustainability
The ECO separately asks project managers to identify the information they need to make planning decisions. Examples:
- Legal and regulatory constraints, industry standards, contract terms.
- Organisational policies, templates, tools and historical data (organisational process assets) and enterprise environmental factors.
- Security and privacy requirements.
- Sustainability requirements: environmental impact (energy, emissions, materials, waste), social impact, and reporting required by the organisation or by regulation.
- Availability and cost of resources, location and time-zone constraints.
- Dependencies on other projects, programmes and operations.
- The decision rights and the people who must approve.
Sustainability can affect scope, supplier selection, costs, and acceptance. In a scenario it may appear as a requirement that the new data centre meets an energy-efficiency target, that suppliers report their emissions, or that packaging reduces waste. The project manager captures it as a requirement or constraint, assesses its impact on cost, schedule, scope and risk, and plans how it will be measured.
Example: sustainability as a planning input
A retailer builds a new distribution centre. The sustainability policy requires annual energy use per parcel to fall by 30% against the current site under comparable operating conditions. It also requires reporting embodied carbon in construction materials. The project manager records these as requirements, asks suppliers to provide emissions data in tenders, adds a measurement activity to the quality plan, and includes a cost line for energy-efficient equipment (estimated at 4% more than the baseline option). The team compares that premium with expected operating savings. The business case is updated to show the whole-life cost.
5. Project execution strategy
The ECO also asks project managers to recommend how to execute and fund the work. The strategy answers how the work will be delivered and funded.
| Aspect | Questions | Examples |
|---|---|---|
| Contracting | Do we do it ourselves or buy it? Which contract type? | Make-or-buy; fixed-price for a stable scope; time-and-materials or capacity-based for uncertain scope |
| Finance | How will it be funded and released? | Stage funding; funding by increments; capital vs operating expense; cost caps |
| Resourcing | Who does the work? | Dedicated cross-functional team; matrix; external consultants; shared services |
| Delivery sequence | In which order will value be released? | Pilot site first; release by region; minimum viable product |
| Risk and reserves | How much uncertainty is covered? | Contingency in the budget; management reserve |
The strategy has to be consistent with the approach. For example, check whether a contract allows scope changes before planning to reorder work. Confirm that shared specialists are available when the schedule requires them.
Example: matching strategy to approach
For the Alder portal, the execution strategy is: a stable internal team of 9 plus 3 specialists from a vendor under a capacity-based contract renewed every three months; funding released per quarterly release with a stage review; a pilot with 2,000 customers before the national launch; a reserve estimated from identified risks, with release authority defined in the funding plan. This supports the hybrid approach: money flows as value is delivered, and the vendor is not locked into a scope that is likely to change.
6. Tailoring
Tailoring means adapting the approach, governance, processes and artefacts to the project's context, the organisation, and the stakeholders. Keep the steps that support decisions, protect outcomes, and meet obligations. See tailoring project communication and reporting for an example of simplifying reports while retaining required fields.
Tailor by considering:
- Project size, risk and criticality: a small internal change does not need the same documents as a large regulated programme.
- Stakeholder needs and expectations.
- Organisation standards: required templates, gates, tools, quality criteria.
- Team skills, location and experience.
- Development approach and life cycle.
What to tailor: the processes that are used, the level of detail in plans, the length of iterations, the review gates, the metrics, the reports and the tools. What not to tailor: legal and regulatory obligations, ethics, and the organisation's mandatory governance (unless the governance body agrees to an exception).
Tailoring is a decision made with the team and key stakeholders, recorded in the plan, and reviewed. A retrospective or a phase review is a natural time to adjust.
Example: tailoring after a review
On the Alder project, the first retrospective shows that the weekly 40-slide steering report takes a day to produce and is not read. The project manager, with the sponsor and the PMO, replaces it by a one-page dashboard (release burn-up, top five risks, decisions needed, budget variance) and a monthly 45-minute review. Mandatory PMO fields stay. The change is documented in the communication plan.
7. Comparing approaches by plan element
Knowing how the approaches handle the main elements helps with scenario questions.
| Element | Predictive | Agile | Hybrid |
|---|---|---|---|
| Scope | Defined up front, WBS, change control | Product backlog, prioritised continuously | Frame fixed; details in backlog |
| Schedule | Baseline, critical path | Time-boxed iterations, release plan | Milestones plus iterations |
| Cost | Baseline with reserves | Funded team capacity per period | Budget cap, release-based funding |
| Quality | Plans, inspection, gates | Definition of done, continuous testing, reviews | Both |
| Risk | Risk register, reviewed regularly | Backlog items, impediments, frequent inspection | Both |
| Stakeholders | Formal reporting | Frequent reviews, product owner | Both |
| Change | Changes to approved baselines follow agreed controls | Reorder work within agreed authority | Check which decisions affect the baseline, contract, or funding |
| Progress | Earned value, milestones | Burn-up/burn-down, velocity, cumulative flow | Combined |
8. Common pitfalls and exam tips
Pitfalls
- Choosing the approach from habit or from what is fashionable, not from assessment.
- Treating agile as "no planning" or "no documentation".
- Treating hybrid as permission to take the worst of both.
- Ignoring regulators, contracts or governance when recommending agile.
- Setting the strategy (contract, funding) in conflict with the approach.
- Forgetting that sustainability and security can be critical inputs.
- Tailoring away something that is mandatory.
- Deciding alone instead of recommending and obtaining agreement.
Exam tips
- In "which approach" questions, find the clues: stable vs uncertain requirements, regulation, customer availability, delivery of early value.
- The best answer usually starts with assessing needs, complexity and magnitude before recommending.
- A fixed date and uncertain scope can suit adaptive or hybrid work. Check how often users can give feedback and whether different parts need different planning and approval practices.
- Tailor to the context; do not impose a method.
- Recommend and obtain agreement; the sponsor or governance body decides.
- Match contract and funding to the approach (agile and a rigid fixed-scope contract are a warning sign).
- When a team with no agile experience is asked to go agile, the best action includes coaching, a pilot, and support from leaders.
9. Mini case study
Situation. Marlow Energy asks you to lead a project to install smart meters for 120,000 customers within 18 months. The meter hardware and the installation procedure are regulated and fixed. The customer app and the data platform that read the meters are new, with unclear requirements and strong pressure from the marketing department to try ideas quickly. The regulator requires monthly progress evidence. Installers are subcontractors paid per installation. The CFO wants a fixed budget of EUR 36 million. The team of platform developers has used Scrum for three years. Sustainability policy requires that old meters are recycled and reported.
Question. What do you recommend?
Model solution.
- Assess. Two parts with different profiles: installation (stable, regulated, repeatable, contract-based) and platform/app (uncertain, benefits from feedback, incremental value).
- Recommend a hybrid approach. A predictive plan for hardware procurement, installation waves by region, regulatory milestones and contracts. An agile product team for the platform and the app, with a backlog prioritised by the product owner and releases aligned to the installation waves.
- Critical information. Regulator requirements and evidence format; recycling requirements and the supplier data to report; data-protection rules for meter readings; installer capacity by region.
- Execution strategy. Fixed-price unit contracts for installation; capacity-based contract for platform development; funding released per installation wave and per platform release; allowances estimated for identified risks, with agreed approval authority for their use.
- Tailor. Monthly regulator report produced from the same data as the programme dashboard; the app team keeps its Scrum events; a joint planning event before each wave aligns both streams; recycling evidence is part of the installation "done" criteria.
- Governance. Steering committee reviews at wave boundaries; escalation thresholds for cost and schedule agreed with the CFO; recommendations documented and approved by the sponsor.
- Review. After wave 1, hold a joint retrospective and adjust the integration and the report.
Why this combination fits. Installation crews need a sequence they can plan with suppliers and approval authorities. App users can evaluate prototypes and guide the next release. Both streams can use feedback and meet their regulatory obligations.
Key terms
- Predictive approach: delivery with relatively stable requirements, substantial early planning, and controls for changes to approved baselines.
- Adaptive / agile approach: iterative and incremental delivery that responds to feedback and change.
- Hybrid approach: a deliberate combination of predictive and agile elements.
- Iterative / incremental: refining through cycles / delivering in usable pieces.
- Complexity: difficulty caused by interacting elements, human behaviour, ambiguity and uncertainty.
- Critical information requirement: information needed early to plan well (regulatory, security, sustainability and others).
- Execution strategy: the way the project will be delivered, contracted, funded and resourced.
- Tailoring: adapting processes, governance and artefacts to the context.
- Minimum viable product (MVP): the smallest release that delivers value and learning.
Summary checklist
- I assess needs, complexity and magnitude with explicit criteria before recommending an approach.
- I can explain predictive, iterative, incremental, agile and hybrid approaches and when each fits.
- I recommend an approach with its justification, and the sponsor or governance body decides.
- I capture critical information requirements, including regulatory, security and sustainability inputs.
- I recommend a project execution strategy (contracting, finance, resourcing) consistent with the approach.
- I tailor processes and artefacts to the context without removing mandatory obligations.
- I review the approach when conditions change.
Official sources
- PMI, PMP Examination Content Outline (July 2026), Process domain, Task 1: https://www.pmi.org/-/media/pmi/documents/public/pdf/certifications/new-pmp-examination-content-outline-2026.pdf (opens in a new tab)
- PMI, New PMP exam (approaches across domains, 40% predictive and 60% agile or hybrid): https://www.pmi.org/certifications/project-management-pmp/new-exam (opens in a new tab)
- PMI, development approaches and hybrid life cycles: https://www.pmi.org/learning/thought-leadership/series/achieving-greater-agility/spectrum-of-approaches (opens in a new tab)
- Manifesto for Agile Software Development: https://agilemanifesto.org/ (opens in a new tab)
- Scrum Guide, Scrum Team and artefacts: https://scrumguides.org/scrum-guide.html (opens in a new tab)
