Agile and Hybrid on the PMP: What the 60% Means

What PMI's 40/60 split says and what it leaves open

The 2026 Exam Content Outline (ECO, revised August 11, 2026, as checked on October 27, 2026) makes four statements about delivery approaches:

• Predictive, adaptive/agile and hybrid approaches appear throughout all three domains and are not tied to any particular domain or task.
• Approximately 40% of items represent predictive approaches.
• The remaining 60% is divided between adaptive/agile and hybrid approaches.
• The exact number of items for each approach may vary by form.

What the outline does not say matters just as much. It gives no split between agile and hybrid, so "60% agile" is a misreading. It does not name Scrum or any other framework, so the PMP is not a Scrum exam. And it does not promise that each question announces its approach. Often you infer it from clues in the stem.

The approach choice itself is tested. Process task 1 includes recommending a development approach, predictive, adaptive/agile or hybrid, after assessing the project's needs, complexity and size. Questions can therefore ask which approach fits before they ask what to do inside it. To see one built that way, try the free approach-choice question on the PMP page, a project with fixed and evolving parts in one plan.

Reading the delivery approach from clues in a PMP stem

One PMP task in three approaches: scope, schedule, change, and reporting

Use the table as a translation key. When a stem describes a change, ask which column you are in before choosing between "submit a change request" and "add it to the backlog for the product owner to order."

Agile terms worth getting exactly right for the PMP

The ECO does not define agile terms, so the precise wording below comes from the November 2020 Scrum Guide and the Agile Manifesto.

• Three accountabilities. A Scrum Team has one Scrum Master, one Product Owner and Developers. The Scrum Guide describes the team as self-managing, meaning members decide internally who does what, when and how.
• Backlog ownership. The Product Owner is accountable for managing the Product Backlog, including ordering it.
• Sprint protection. Sprints are one month or less. No changes are made that would endanger the Sprint Goal, though scope may be clarified and renegotiated with the Product Owner as more is learned.
• Daily Scrum. A 15-minute event for the Developers, not a status report to a manager.
• Impediments. The Scrum Master serves the team partly by causing impediments to be removed.
• Values behind agile. The Manifesto's fourth value pair reads "Responding to change over following a plan," and its authors add that they still see value in the items on the right.

The ECO uses its own vocabulary in places. Process task 8, for example, names story points as one way to estimate. Learn the concepts, then match them to whatever words a question uses.

A worked hybrid PMP scenario: fixed regulatory date, iterative build

This scenario is invented. Brightline Mutual, a fictional regional insurer, is replacing its claims portal. A regulator requires a new quarterly claims report file by June 30. Policyholders also want a simpler way to file a claim from their phones.

The project manager splits the work by its nature:

1. Regulatory reporting interface: predictive. The scope is fixed by the regulator, the date is fixed, and an audit follows. It gets a baselined plan, a critical path through data mapping, testing and sign-off, and formal change control.
2. Mobile claim flow: agile. Requirements will evolve with user feedback, so a product owner orders a backlog and the team delivers in two-week sprints.

Three events follow in month two:

• The claims team asks for a photo-upload feature. That is new policyholder-facing scope, so it goes to the backlog for the product owner to order. No change board meeting is needed.
• The regulator publishes a clarification that adds one field to the report. That changes fixed, baselined scope, so it goes through change control with an impact assessment against the June 30 milestone. This is Business Environment task 3 (change control) meeting task 8 (external change).
• The sponsor asks for status. The project manager reports the reporting interface against its milestone plan and the claim flow with a release burn-up chart, one view per workstream.

A question built on this case might ask what to do first about the regulator's clarification. The strong answer assesses its impact and runs it through the change control process. The distractor that gives it to the product owner to order treats a fixed regulatory item as if it were ordinary backlog work.

After working through Brightline, try writing the same three events for a project you know. Full PMP prep on Passy is not open yet; the PMP page describes practice that mixes approaches inside every domain, planned for launch.

Where agile and hybrid show up across the three PMP domains

Because approaches are spread across domains, expect them in every kind of question:

• People. Leading a self-managing team, choosing a leadership style, building shared ground rules. The PMP team leadership guide covers these.
• Process. Choosing the approach, breaking down scope as a backlog or a WBS, prioritizing by value, estimating in story points. See the PMP Process domain overview.
• Business Environment. Change control in predictive vs adaptive work, removing impediments, reassessing the backlog when regulations or markets shift.

The PMP scenario-question method shows how to read the approach out of a stem before choosing. For the wider July 2026 update, including the domain weights, see the PMP exam 2027 guide. To build the habit in short sessions, start with the free PMP practice questions and name the approach before you read the options. When you want more volume, compare the free set with the full PMP prep planned for launch.