How do the three approaches compare?
The approaches differ in how work is planned, how feedback changes it and how decisions are controlled. Predictive planning is useful when the work and constraints can be defined early. Agile approaches use feedback to refine what should be built next. Hybrid work chooses where each approach is useful.
The labels don’t tell you whether a project is well managed. A badly maintained baseline and an unordered backlog can both leave a team confused. Look for clear responsibilities, useful feedback and control suited to the work.
PMI’s current outline includes all three approaches across its exam areas. Don’t treat agile as a small optional topic at the end of your plan.
Scroll sideways to see every column.
| Approach | Planning pattern | Typical decision clue |
|---|---|---|
| Predictive | Define scope and establish baselines | Assess a request against approved constraints |
| Agile | Deliver, inspect and adapt | Order upcoming work from value and feedback |
| Hybrid | Combine controls and feedback cycles | Identify which part of the project is affected |
Does predictive mean that changes are forbidden?
No. Predictive work allows change through the project’s agreed control process. The point of a baseline is to make the impact visible, not to make every new need invalid.
An example is a clinic fit-out with approved room layouts. A new accessibility need may be valuable and necessary, but the team must check design, cost, safety and schedule impacts before changing construction work.
Use the change-request guide to distinguish evaluating a request from approving it. A project manager may coordinate the analysis without holding authority to approve every resulting change.
Does agile mean that the team can change anything at any time?
No. Agile work uses defined responsibilities, goals and feedback; it does not remove accountability or allow random changes. In Scrum, the Product Owner orders the Product Backlog, and Developers plan the work needed to reach the Sprint Goal.
During a Sprint, scope can be clarified and renegotiated with the Product Owner as more is learned, without endangering the Sprint Goal. The Scrum Guide describes these responsibilities.
A stakeholder’s urgent request may deserve discussion, but it doesn’t become an instruction to interrupt any developer immediately. Read the Scrum roles guide before turning agile into a shortcut for skipping a decision process.
What does a hybrid project look like?
A hybrid project uses different approaches where the work needs them, with a clear link between the parts. For example, a transport organization might manage a fixed installation window with predictive controls while developing its passenger-information software through short feedback cycles.
The software backlog can change, but a late software decision may affect installation training or testing. The project manager needs to connect those impacts instead of pretending the two parts are independent.
In a question, identify the part affected by the problem. Hybrid is not a third answer process that applies identically to every decision. A request affecting an approved installation milestone may need a different route from a low-priority software backlog change.
How should I study approach questions for the PMP?
Study approach questions by changing the context of one problem and explaining how the response changes. That gives you a transferable distinction rather than a list of predictive and agile keywords.
Try a stakeholder asking for a new reporting view. With a baselined reporting package, assess the formal change impacts. With an upcoming backlog item, discuss value and order it through the responsible role. With a hybrid rollout, also check dependencies on training and release dates.
PMP Exam Coach’s agile simulator and scenario previews are designed to help practice these tradeoffs. Compare them with the free situational-question guide.
