When to Use Agile vs Predictive vs Hybrid Approaches on the PMP Exam

The Most Important Question on the PMP Exam

"What approach should this project use?" may be the single most important judgment call a project manager makes — and the PMP exam tests it repeatedly. PMI expects candidates to evaluate project characteristics and select the most appropriate lifecycle: predictive, agile, hybrid, or somewhere on the spectrum between them.

Understanding the Spectrum

PMI doesn't present methodology selection as an either/or choice. Instead, they describe a continuum from fully predictive to fully agile, with many valid positions in between. Your job is to determine where a given project should fall on that spectrum based on its unique context.

When to Use a Predictive Approach

A predictive (waterfall) approach works best when:

• Requirements are well-defined and stable. The stakeholders know exactly what they want, and it's unlikely to change significantly.
• The technology is well-understood. The team has built similar things before and knows the technical path forward.
• Regulatory compliance requires detailed documentation. Industries like construction, pharmaceuticals, and aerospace often mandate comprehensive documentation and formal approvals at specific phases.
• The project has a fixed scope and budget. Contractual obligations may require committing to specific deliverables at a fixed price.
• Sequential dependencies are inherent. You can't install electrical wiring before the walls are framed. Some work is genuinely sequential.

Predictive Examples

Building a bridge, constructing a data center to published specifications, implementing a well-defined regulatory reporting system, executing a proven manufacturing process.

When to Use an Agile Approach

An agile approach works best when:

• Requirements are unclear or expected to change. The end users aren't sure what they want until they see it. Discovery is part of the process.
• Rapid feedback is possible and valuable. Users can evaluate working increments and provide feedback that shapes future development.
• The team is cross-functional and co-located (or effectively co-located). Agile relies on close collaboration and fast communication.
• Time to market matters more than comprehensive scope. Getting a working product to customers quickly provides competitive advantage.
• Innovation and creativity are required. The team needs freedom to experiment, learn, and adapt.

Agile Examples

Developing a new mobile app, creating a product for an emerging market, building a platform where user needs are still being discovered, research and development projects.

When to Use a Hybrid Approach

A hybrid approach works best when:

• Different project phases have different characteristics. Requirements gathering might be exploratory (agile), but deployment might be sequential (predictive).
• The organization is transitioning from predictive to agile. Hybrid provides guardrails while teams build agile maturity.
• Some components have stable requirements while others don't. The infrastructure is well-defined (predictive) but the user interface is evolving (agile).
• Stakeholders need predictive-style governance with agile-style delivery. Board reporting follows a predictive cadence; development follows sprints.

Hybrid Examples

An ERP implementation with predictive planning but agile customization, a product launch with agile development and predictive marketing milestones, a government project with compliance gates but iterative delivery.

The Decision Framework

When the PMP exam presents a scenario and asks which approach is best, evaluate these factors:

1. Requirements stability — High stability favors predictive. Low stability favors agile.
2. Stakeholder availability — Frequent engagement possible? Agile. Stakeholders unavailable until milestones? Predictive or hybrid.
3. Risk tolerance — High risk from late integration favors agile. High risk from scope changes favors predictive.
4. Delivery urgency — Need value delivered early? Agile or incremental. Can wait for full delivery? Predictive is viable.
5. Team experience — Team experienced with agile? Full agile. Team new to agile? Hybrid with training.
6. Organizational culture — Culture supports autonomy and experimentation? Agile. Culture requires hierarchy and formal processes? Start hybrid.

The Exam Strategy

Never assume one approach is universally correct. The exam rewards contextual judgment. Read the scenario carefully, identify the characteristics that point toward each approach, and choose the answer that best matches the situation described.

Also watch for the word "tailoring" — PMI loves it. The best project managers tailor their approach to the project, not force the project into a methodology.

Build your methodology selection judgment with realistic scenarios on PMPprep. Browse all agile and hybrid topics in our topics library.