Quick answer: Development-approach questions test whether you can read a scenario's signals — regulatory weight, requirement stability, delivery cadence — and recommend predictive, agile, or hybrid based on the situation, not preference. They come from Process domain task PRO-T1, which also covers building the integrated plan, checking it for dependencies and gaps, and keeping it current. The exam's content mix is about 40% predictive and 60% agile and hybrid, so you need to reason in all three modes.
Every project on the exam happens inside a development approach, so this choice shapes far more than the questions that ask about it directly. When a stem asks what to do about a scope request or a missed dependency, the right answer often depends on which approach the project is running — and PRO-T1 is where the exam tests whether you can make and defend that call. This guide covers the signals that point to each approach, the rest of the task, and two scenario walk-throughs.
What PRO-T1 actually covers
PRO-T1 in the 2026 ECO is the Process domain's planning backbone: develop an integrated project management plan and plan delivery. That's broader than picking a methodology. The task asks you to assess the project's needs and complexity, recommend a development approach that fits, identify critical information requirements (sustainability is named explicitly), build an execution strategy, consolidate subsidiary plans into one integrated plan, estimate effort and resources, assess the consolidated plan for dependencies, gaps, and continued business value, and maintain it with data-informed decisions.
The Process domain carries 41% of the exam, the largest share, and PRO-T1 sits at the front of it because everything downstream — scope, schedule, resources, quality — inherits the approach decision. For the full task map, see the Process domain guide.
75 free questions, scored against the new domain weights. No card required.
The signals in a stem: what points where
The exam almost never says "this project is predictive." It gives you facts and expects you to infer the approach — or to notice that the facts argue against the one the team picked. Train yourself to spot these signals:
| Signal in the stem | Points predictive | Points agile | Points hybrid |
|---|---|---|---|
| Requirements | Stable, fully known up front | Evolving, discovered through feedback | Some fixed, some evolving |
| Regulatory or contractual weight | Heavy documentation, formal sign-offs, audits | Light, few external mandates | Regulated core plus flexible components |
| Delivery cadence | One delivery at the end, or few milestones | Frequent increments, early value | Staged gates with iterative work inside |
| Change tolerance | Change is costly; rework is expensive (physical builds) | Change is cheap; software-like work | Varies by component |
| Stakeholder involvement | Reviews at defined gates | Continuous collaboration | Mixed by workstream |
| Prior experience | Organization has done this before | Novel problem, high uncertainty | Familiar frame, uncertain content |
Two habits make this table usable under time pressure. First, no single signal decides it — weigh the set. A regulated project with genuinely evolving requirements is a hybrid argument, not a predictive one. Second, watch for the mismatch pattern: many stems describe a team running one approach while the signals argue for another, and the best response is usually to surface the mismatch, not push harder with the wrong tool. The 40/60 content split is covered in our guide to the predictive-agile balance.
Hybrid: the answer that requires the most precision
Hybrid is where careless candidates lose points, because "a bit of both" feels safe. The exam expects more precision: hybrid means deliberately assigning different approaches to different parts of the project based on each part's characteristics — not waterfall with a daily standup bolted on. The structures the exam rewards: predictive gates around agile delivery (phase reviews and funding gates kept, sprints between them), a split by component (the regulated or physical portion predictive, the software portion agile), or a split by phase (iterative discovery, locked-down build).
When a stem asks you to defend a hybrid recommendation, the winning rationale names which parts get which treatment and why. "We'll use hybrid because it's flexible" is a distractor-quality answer; "the compliance deliverables follow a stage-gated plan because sign-off order is mandated, while the user-facing modules iterate because requirements are still emerging" is the shape of a correct one. For how gates, sprints, and governance fit together, see the hybrid project management guide.
Beyond the choice: dependencies, gaps, and business value
Once the approach is set, PRO-T1 shifts to the integrated plan — the part of the task candidates under-study. The exam tests whether you review the consolidated plan the way an experienced PM does.
Dependencies. Consolidation surfaces cross-workstream dependencies: the training plan assumes software the schedule delivers later, two teams count on the same test environment in the same window. Stems here reward checking the consolidated plan for sequencing conflicts before committing to dates.
Gaps. A gap is work the outcome requires that no plan owns — data migration nobody scoped, an operational handover with no owner. The exam pattern: find the gap during plan review and resolve ownership, not in execution.
Business value. A plan can be internally consistent and still not worth executing. PRO-T1 expects you to check that it still delivers the value the project was chartered for — and to raise it, not bury it, when scope trades or delays have eroded the case.
Critical information requirements sit here too, with sustainability called out in the 2026 ECO. If a stem states environmental impact or long-term operating cost as a project requirement, the plan must capture and monitor it like any other requirement.
Keeping the plan current
The last slice of PRO-T1 is maintenance: the plan is a living document on every approach, not just agile. When reality diverges, update the plan through the proper mechanism — change control on predictive work, backlog reprioritization on agile work — and base the update on data rather than optimism or pressure. Stems treat a stale plan as a real failure state: teams working from old baselines, reports nobody trusts. The corrective action is to bring the plan back to truth first, then manage forward.
This is also where PRO-T1 meets tailoring — sizing the planning effort itself to the project, so a small internal effort isn't buried under enterprise-grade artifacts. That theme is big enough that we cover tailoring separately.
Scenario walk-throughs
Read each stem, form your answer, then check the reasoning.
Scenario 1: The approach recommendation
You're assigned to lead a project delivering a patient-monitoring device: physical hardware that must pass a regulator's staged approval process, plus a companion mobile app whose feature set the sponsor expects to evolve from clinician feedback during development. The hardware requirements are fixed by the approved design dossier, and any change triggers regulatory resubmission. The sponsor asks you to recommend a development approach for the project as a whole.
What the exam wants: Read the signals per component instead of averaging them. The hardware has fixed requirements, expensive change, and a mandated sign-off order — predictive signals. The app has evolving requirements and a feedback loop — agile signals. Pure predictive would choke the app's learning cycle; pure agile would put regulatory sign-offs at risk. The best response is hybrid with the reasoning explicit: the device workstream follows a stage-gated predictive plan aligned to approval milestones, the app workstream iterates on clinician feedback, and the integrated plan defines how the two synchronize where app releases depend on hardware availability.
Scenario 2: The consolidated-plan review
You've consolidated subsidiary plans from four workstream leads into a draft integrated plan for a warehouse-automation rollout. During your review you notice the training plan assumes the final control software reaches the training environment six weeks before go-live — while the software schedule shows delivery only one week before go-live. Both leads signed off on their own plans. The steering committee expects the integrated plan tomorrow.
What the exam wants: This is a dependency conflict found exactly where PRO-T1 says to look — in the consolidated view, where no single workstream could see it. The tested behavior is to resolve it before baselining: bring the two leads together, confirm the real constraint, and rework the sequence (a phased software drop for training, adjusted dates, or a revised go-live). Submitting on time with a known broken dependency is wrong; so is quietly changing one workstream's dates without its owner, and so is escalating to the steering committee as the first move — this sits within the PM's authority to facilitate. Deadline pressure in a stem is usually a distractor: the exam rewards surfacing the problem over shipping a plan you know is wrong.
How to practice this task
Approach reasoning shows up beyond dedicated PRO-T1 items — it's baked into case sets, where one scenario's approach shapes five linked questions, a format the case section guide covers. The reliable way to build the skill is repetition against scored scenarios: answer, miss, see the signal you skipped, then meet the same pattern again before you forget it. ExamElephant's bank is written to the 2026 ECO, and the retest engine returns each miss at three days and again at seven until you've answered it correctly twice in a row. Start with 75 free questions — no card required — and find out how your approach-reading holds up.
Paid passes are coming soon
PMP pass: $100. One payment, study until you pass (up to 12 months), nothing renews. The full 2,100-question bank, timed 180-question mock exams and unlimited tutoring. Leave your email and we'll tell you the day it opens. Unsubscribe anytime. Privacy
FAQ
How many questions on the PMP exam are about choosing a development approach?
PMI doesn't publish per-task question counts. What is published: the Process domain carries 41% of the exam, and the content mix is about 40% predictive and 60% agile and hybrid. Approach reasoning also appears indirectly, since many situational questions can only be answered once you've inferred which approach the project is running.
Is hybrid usually the correct answer on development-approach questions?
No. Hybrid is correct when the stem's signals genuinely split — some components with fixed, regulated requirements and others with evolving ones. When the signals point one way, the one-way answer wins. Picking hybrid as a hedge is a recognizable wrong-answer pattern.
What's the difference between choosing a development approach and tailoring?
Choosing the approach is the first, biggest decision: predictive, agile, or hybrid for each part of the project. Tailoring is the finer-grained work that follows — sizing processes, artifacts, ceremonies, and governance to the project's scale, risk, and context. The exam tests both, and a mismatch in either direction can be the flaw a stem asks you to spot.
Who decides the development approach on a project?
On the exam, the project manager assesses needs and complexity and recommends the approach, typically with the team and key stakeholders, within any constraints the organization or contract imposes. Stems that show an approach imposed with no assessment — or a PM ignoring organizational gate requirements — are usually setting up the flaw the question wants you to catch.