Predictive (plan-based) project management is a structured approach where the entire project is planned in detail before any execution work begins. It matters for the CAPM exam because it is the traditional, widely-used methodology that many organisations still rely on, and it forms the foundation for understanding more flexible methods like agile. You need to recognise its fixed sequence of phases, its heavy reliance on upfront documentation, and the trade-offs it makes between flexibility and predictability.
Jump to a section
A simple way to picture Predictive (Plan-Based) Project Management Overview
A wedding reception is a project that demands a predictive, plan-driven approach. The bride and groom set a fixed date, a strict budget, and a clear guest count before any work begins. The caterers cannot start preparing meals without knowing the exact number of guests and their dietary restrictions. The venue must be booked months in advance, and the seating chart created before the invitations can be printed. Every major decision depends on a prior plan being approved. The project manager, often the wedding planner, creates a detailed schedule with milestones: finalise the guest list by week one, book the venue by week four, send invitations by week eight, confirm the menu by week ten. Changes after the invitations go out cause chaos and cost money. If a guest cancels last minute, the plan has a buffer of a few no-shows built in, but the overall scope and timeline remain fixed. The entire event runs on a waterfall of sequential tasks: you cannot send invitations before you know the venue, and you cannot arrange the seating before you have the RSVPs. This plan-first, execute-later approach mirrors predictive project management in IT, where requirements are fully defined upfront, and the team follows a phased schedule with minimal change once execution begins.
Predictive project management, often called the waterfall model, is a methodology where a project is broken down into distinct, sequential phases. Each phase must be completed fully before the next one begins. This contrasts with agile methods, where work is done in small iterative cycles. The core idea is that by investing time and effort into detailed planning at the start, you reduce uncertainty and risk during execution.
The approach is called 'predictive' because the team predicts the entire scope, schedule, and budget upfront. The plan then acts as a baseline against which actual progress is measured. Any deviation from the plan is treated as a problem that needs to be corrected. This predictability is the methodology's greatest strength for projects with clear, stable requirements.
For the CAPM exam, you need to understand the typical phases of a predictive project. The Project Management Institute (PMI) defines five process groups that apply to predictive projects, though they are not always perfectly sequential. They are: Initiating, Planning, Executing, Monitoring and Controlling, and Closing. In a predictive project, the Planning process group consumes a large portion of the project's time and budget upfront, often 20-40% of the total effort.
A key characteristic is the Work Breakdown Structure (WBS). The WBS is a hierarchical decomposition of the total scope of work into smaller, manageable components called work packages. Think of it like a detailed recipe: you break down 'bake a cake' into 'mix dry ingredients', 'cream butter and sugar', 'add eggs', 'bake at 180C for 30 minutes', and 'frost'. Each component is a work package that can be assigned, estimated, and tracked.
Another critical feature is the use of a critical path. The critical path is the longest sequence of dependent tasks in the project schedule. It determines the shortest possible time to complete the project. If any task on the critical path is delayed, the whole project completion date slips. For example, in building a house, you cannot start the roof until the walls are up, and you cannot start the walls until the foundation is poured. The foundation, walls, and roof form part of the critical path.
Change management in predictive projects is formal and rigid. Any proposed change goes through a Change Control Board (CCB), a group of stakeholders who approve or reject changes. This is to protect the baseline plan. A change request must describe the proposed change, its impact on scope, schedule, cost, and quality. This reduces scope creep, which is uncontrolled expansion of the project's scope without adjusting time or budget.
Why does this approach exist? It arose from manufacturing and construction industries, where rework is extremely expensive. In software development, it became popular in the 1970s and 1980s. It replaces ad-hoc, chaotic development with discipline and structure. However, it is not suitable for projects where requirements are uncertain or likely to change, because the cost of changing direction late in the project is very high. The PMBOK Guide, which is the basis for the CAPM exam, describes predictive life cycles as one of the three main life cycle types, alongside iterative and adaptive (agile).
Key advantages of predictive project management include:
Clear, well-defined stages with specific deliverables at each gate.
Easy to measure progress against a fixed schedule and budget.
Works well for projects with low uncertainty and stable requirements.
Provides a detailed blueprint for new team members to understand the project.
Simplifies resource planning because tasks are known far in advance.
Key disadvantages include:
Inflexibility: changes are difficult and expensive.
Customers do not see working results until late in the project.
High risk of delivering something the customer no longer wants if requirements change.
Heavy documentation overhead can slow down the team.
Initiating Phase
The project is formally authorised. A project charter is created, which defines the high-level scope, objectives, and key stakeholders. The project manager is assigned. This phase answers the question: 'Should we do this project?'
Planning Phase
The most detailed phase in a predictive project. The team creates the full scope statement, Work Breakdown Structure, schedule, budget, risk register, and communication plan. This phase can take 20-40% of the project's total time. The deliverables are baselines that will be measured against during execution.
Executing Phase
The team completes the work defined in the project management plan. This includes building the product, holding meetings, managing quality, and developing the team. In a predictive project, execution is a linear process moving through sequential stages.
Monitoring and Controlling Phase
This phase runs in parallel with executing. It involves tracking progress against the baseline, managing changes, and taking corrective action. Key tools include earned value management, variance analysis, and formal change requests.
Closing Phase
The project is formally completed. This includes finalising all activities, handing over the deliverable to the customer, releasing project resources, and documenting lessons learned. The project is archived, and the contract is closed.
An IT professional using predictive project management might be tasked with implementing a new payroll system for a large company. The requirements are well understood because payroll regulations are fixed by law, and the company's internal policies are stable. The project manager begins by gathering all detailed requirements from the HR department, finance team, and legal advisors. These requirements are documented in a requirements traceability matrix, which links each requirement to its source and to the test cases that will verify it.
Next, the project manager creates a Work Breakdown Structure. For the payroll system, the top-level WBS items might include: 'System Architecture', 'Database Design', 'User Interface', 'Testing', 'Data Migration', 'Training', and 'Go-Live Support'. Each of these is broken down into work packages. For example, 'Testing' might include 'Unit Testing', 'Integration Testing', 'User Acceptance Testing', and 'Performance Testing'. Each work package is assigned to a team member, estimated in hours, and given a deadline.
The schedule is then built using the critical path method. The project manager identifies dependencies: you cannot do integration testing until unit testing is complete. You cannot start user acceptance testing until the integrated system is stable. Data migration must happen before go-live but after the database is built. The critical path might run through database design, integration, and user acceptance testing. Any delay in database design would push the entire project.
Throughout execution, the project manager holds weekly status meetings and tracks progress against the baseline schedule using earned value management (EVM). EVM compares how much work was planned to how much has actually been completed and at what cost. If the project is behind schedule, the manager might request additional resources to catch up, but only if the budget allows.
When a stakeholder requests a change — for example, adding a new report type — the project manager processes it through the formal change control system. A change request is submitted, the impact is assessed (e.g., adding the report would extend the schedule by two weeks and cost an extra £10,000), and the Change Control Board decides. If approved, the baseline is updated. If rejected, the report is not added.
Finally, when the system passes all tests and is deployed, the project enters closing. A lessons learned document is created, capturing what went well and what could be improved. The project is formally handed over to operations, and the team is released. This step-by-step, disciplined approach ensures that the payroll system is reliable, compliant with regulations, and delivered on time and within budget.
The CAPM exam tests your understanding of predictive project management primarily through questions about its characteristics, advantages, and typical phases. You will not be expected to manage a project, but you must be able to identify the correct methodology based on a given scenario. The exam loves to test the differences between predictive and agile life cycles.
Common question types include:
Scenario-based questions: You are given a description of a project (e.g., 'a construction project with fixed requirements and strict regulatory approval gates') and asked which life cycle is most appropriate. The correct answer is predictive.
Phase identification: They will list phases or process groups and ask which one is the first or last in a predictive project. For example, 'Closing' is the final process group.
Characteristics of a Work Breakdown Structure: Questions about how the WBS is created, its purpose, and what a work package is.
Critical path: You may need to calculate the duration of the critical path from a simple network diagram. They often set traps with slack or float, asking which task has the least float (the answer is tasks on the critical path).
Change control: Questions about the purpose of a Change Control Board, what a change request must include, and the consequences of not following change control.
Traps the exam sets:
They will try to trick you into thinking predictive is always better than agile. It is not. Predictive is better for stable requirements, agile for evolving ones.
They will describe a project that looks predictive but has a key agile characteristic, such as incremental delivery. Know that predictive delivers once at the end.
They will ask about 'rolling wave planning' which is actually a progressive elaboration technique used in both predictive and agile, but is most often associated with predictive for near-term detail. Be careful.
Key definitions to memorise for the exam:
Baseline: The approved version of a schedule, scope, or cost plan used for comparison during execution.
Work package: The lowest level of the WBS, a manageable unit of work.
Critical path: The longest path through the project network diagram; determines the minimum project duration.
Change Control Board (CCB): A formally constituted group of stakeholders responsible for approving or rejecting changes to the project plan.
Scope creep: Uncontrolled changes or continuous growth in a project's scope.
The exam will also ask about the five process groups and how they relate to predictive phases. Remember: in a predictive project, these process groups are performed in a linear fashion, though they may overlap slightly. Planning is front-loaded. Monitoring and Controlling runs in parallel with Executing.
Predictive project management requires all requirements to be defined and approved before execution begins.
The five process groups in predictive projects are Initiating, Planning, Executing, Monitoring and Controlling, and Closing.
The Work Breakdown Structure (WBS) decomposes the total project scope into manageable work packages.
The critical path is the longest sequence of dependent tasks and determines the shortest possible project duration.
Changes in a predictive project are managed through a formal Change Control Board (CCB) to protect the baseline.
Predictive life cycles are best suited for projects with low uncertainty, stable requirements, and strict regulatory compliance.
Scope creep refers to uncontrolled changes to project scope without corresponding adjustments to time, cost, or resources.
These come up on the exam all the time. Here's how to tell them apart.
Predictive (Waterfall)
Requirements are fully defined upfront before development
Planning is a single large phase at the start
Customer sees final deliverable at the end
Agile (Scrum)
Requirements evolve throughout the project
Planning is done in small cycles each sprint
Customer sees working increments every 2-4 weeks
Predictive Project
Delivers the entire product once at project end
Feedback from early cycles does not change the plan
Phases are sequential (do not repeat)
Iterative Project
Delivers in repeated cycles, improving each time
Feedback from each cycle is used to refine the product
Phases repeat (design, build, test in cycles)
Work Breakdown Structure (WBS)
Describes what will be delivered (scope)
Is a hierarchical list of deliverables
Does not contain dates or durations
Project Schedule
Describes when work will happen (time)
Is a timeline with start and finish dates
Contains duration estimates and dependencies
Critical Path Method (CPM)
Uses a single deterministic time estimate per task
Focuses on the longest path of dependencies
Commonly used in construction and manufacturing
Program Evaluation and Review Technique (PERT)
Uses three time estimates (optimistic, pessimistic, most likely)
Focuses on probabilistic duration and risk
Commonly used in research and development projects
Change Control Board (CCB)
Is a group of stakeholders who approve or reject changes
Changes are evaluated against the baseline plan
Formal documentation (change request) is required
Product Owner (Agile)
Is a single person who prioritises the backlog
Changes are evaluated against business value
Formal documentation is minimal; changes are discussed in meetings
Mistake
Predictive project management means you cannot change anything once the plan is approved.
Correct
Changes can be made, but they go through a formal change control process. The baseline is updated only after approval, not locked forever.
Beginners hear 'fixed plan' and assume zero flexibility. In reality, predictive projects have robust change management precisely because change is inevitable.
Mistake
The Waterfall model and predictive project management are completely different things.
Correct
Waterfall is one specific implementation of a predictive life cycle. The CAPM exam treats them as synonymous in many contexts.
Waterfall is a software-specific term from the 1970s, while predictive is a broader PMI term. Students confuse the history with the current conceptual framework.
Mistake
In a predictive project, the customer sees a working product early in the project.
Correct
The customer typically sees the final product only during the testing or deployment phase, near the end.
People assume 'progress updates' are the same as 'working increments'. In predictive, progress is shown through documentation and prototypes, not functioning deliverables.
Mistake
The critical path is the list of all the most important tasks in the project.
Correct
The critical path is the longest sequence of dependent tasks that determines the project's minimum duration. It is not about importance, but about schedule dependency.
The word 'critical' implies importance, so beginners assign priority meaning. The exam tests the technical definition of dependency length.
Mistake
A Work Breakdown Structure is the same as a project schedule.
Correct
The WBS is a hierarchical list of scope deliverables, not a timeline. The schedule shows when each WBS element will be done.
Both documents are created during planning, and both use hierarchical numbering. Beginners mix up structure (what) with timeline (when).
Mistake
Predictive project management is obsolete and never used in modern IT.
Correct
Predictive is still widely used in industries with regulatory constraints, fixed-price contracts, or stable requirements, such as construction, manufacturing, and some government IT projects.
The popularity of agile methods in software startups creates a false impression that predictive is dead. The CAPM exam acknowledges both are valid in different contexts.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
It is a project management approach where you plan everything in detail before you start doing the work. You decide the full scope, schedule, and budget upfront, and then follow the plan closely.
Yes, for the CAPM exam, they are essentially the same concept. Waterfall is a specific historical term for a predictive life cycle used in software development. Both describe a sequential, phase-based approach.
Use predictive when the requirements are clear, stable, and unlikely to change. Also use it when the project is large, complex, and has strict regulatory or contractual constraints, such as building a bridge or implementing a payroll system.
A WBS is a chart that breaks the total project work into smaller, manageable pieces called work packages. It is like a detailed to-do list organised by deliverable, not by time. It only includes what needs to be done, not when.
The critical path is the longest chain of tasks that are dependent on each other. It determines the shortest possible duration of the project. If any task on the critical path is delayed, the whole project is delayed.
Yes, but changes go through a formal process called change control. A change request is submitted, its impact is assessed, and a Change Control Board decides whether to approve it. Uncontrolled changes cause scope creep.
They are Initiating, Planning, Executing, Monitoring and Controlling, and Closing. In a predictive project, these happen in a linear order, with Planning being the most intensive phase.
You've finished Predictive (Plan-Based) Project Management Overview. Continue through the CAPM study guide to build a complete picture of the exam.
Done with this chapter?