Key Takeaways

  • The predictive lifecycle consists of five process groups: Initiating (2%), Planning (24%), Executing (31%), Monitoring & Controlling (25%), and Closing (8%)
  • Phase gates (stage gates or kill points) are formal review checkpoints where go/no-go decisions are made before proceeding to the next phase
  • Predictive approaches work best when requirements are well-defined upfront and unlikely to change significantly during execution
  • Sequential execution means each phase must be substantially complete before the next phase begins, minimizing rework but reducing flexibility
  • Approximately 40% of PMP exam questions (as of July 2026) involve predictive approaches, making this essential knowledge for certification
Last updated: January 2026

Predictive Lifecycle

The predictive lifecycle, also known as the waterfall or traditional approach, is a plan-driven methodology where the project scope, schedule, and cost are determined early in the project and changes are carefully controlled. This approach has been the foundation of project management for decades and remains essential knowledge for PMP certification.

Understanding the Predictive Approach

In a predictive lifecycle, the project progresses through a series of sequential phases, with each phase building upon the deliverables of the previous one. The key characteristic is that significant planning occurs upfront, and the project team follows a detailed plan throughout execution.

Key Characteristics of Predictive Projects

CharacteristicDescription
RequirementsDefined upfront and relatively stable
PlanningComprehensive planning before execution begins
PhasesSequential, with formal handoffs between phases
ChangesControlled through formal change management
DeliverablesProduced at the end of phases or project
DocumentationExtensive documentation throughout

The Five Process Groups

PMI organizes project management into five process groups that represent the logical progression of project activities. While not strictly phases, these groups provide a framework for understanding how work flows in predictive projects.

Process Group Distribution

Process GroupApproximate % of EffortFocus
Initiating2%Project authorization, stakeholder identification
Planning24%Defining scope, schedule, cost, quality, and other plans
Executing31%Performing the work to create deliverables
Monitoring & Controlling25%Tracking progress, managing changes
Closing8%Formal acceptance, lessons learned, release resources

Initiating Process Group

The Initiating process group establishes the foundation for the project:

Key Activities

  • Develop Project Charter — The formal document that authorizes the project and gives the project manager authority
  • Identify Stakeholders — Determine who has interest in or influence over the project
  • Define High-Level Scope — Establish what the project will and will not include
  • Assign Project Manager — Officially designate the person responsible for project success

Outputs

  • Project Charter
  • Stakeholder Register
  • Assumption Log

Planning Process Group

The Planning process group involves the most intensive work in predictive projects:

Key Planning Activities

Knowledge AreaKey Planning Outputs
ScopeScope Management Plan, WBS, Requirements Documentation
ScheduleSchedule Management Plan, Project Schedule, Network Diagram
CostCost Management Plan, Cost Baseline, Budget
QualityQuality Management Plan, Quality Metrics
ResourcesResource Management Plan, Team Charter
CommunicationsCommunications Management Plan
RiskRisk Management Plan, Risk Register
ProcurementProcurement Management Plan, Procurement Documents
StakeholderStakeholder Engagement Plan

The Project Management Plan

All subsidiary plans combine to form the comprehensive Project Management Plan, which serves as the roadmap for project execution.


Executing Process Group

The Executing process group is where the actual work gets done:

Key Activities

  • Direct and Manage Project Work — Perform activities defined in the project management plan
  • Manage Quality — Execute quality assurance activities
  • Acquire and Develop Team — Obtain and train project team members
  • Manage Communications — Distribute project information to stakeholders
  • Implement Risk Responses — Execute planned risk response actions
  • Conduct Procurements — Obtain seller responses and award contracts

Monitoring & Controlling Process Group

This process group runs throughout the project to track performance and manage changes:

Key Activities

  • Monitor and Control Project Work — Track overall project performance
  • Perform Integrated Change Control — Review and approve/reject change requests
  • Validate Scope — Obtain formal acceptance of completed deliverables
  • Control Scope, Schedule, Cost — Compare actual performance to baselines
  • Monitor Risks — Track identified risks and identify new ones
  • Control Procurements — Manage vendor relationships and contracts

Performance Reporting

Regular status reports compare actual progress against the performance measurement baseline (scope, schedule, cost baselines combined).


Closing Process Group

The Closing process group formally completes the project or phase:

Key Activities

  • Close Project or Phase — Finalize all activities across all process groups
  • Obtain Final Acceptance — Get formal sign-off from the customer/sponsor
  • Document Lessons Learned — Capture what worked and what could be improved
  • Release Resources — Return team members to functional departments
  • Archive Project Documents — Store documents for future reference
  • Close Procurements — Complete and settle vendor contracts

Phase Gates and Stage Gates

Phase gates (also called stage gates or kill points) are formal review checkpoints at the end of each phase:

Purpose of Phase Gates

  • Go/No-Go Decision — Determine whether to proceed, modify, or terminate the project
  • Quality Check — Verify that phase deliverables meet quality standards
  • Resource Allocation — Approve resources for the next phase
  • Alignment Check — Ensure project still aligns with business objectives

Phase Gate Review Criteria

CriterionQuestions Asked
Business ValueDoes the project still provide expected value?
Technical FeasibilityCan we technically deliver as planned?
Resource AvailabilityDo we have the resources for the next phase?
Risk AssessmentAre risks acceptable?
Schedule/BudgetAre we on track for planned completion?

When to Use Predictive Approaches

Predictive methodologies are best suited for projects with specific characteristics:

Ideal Conditions for Predictive

ConditionWhy Predictive Works
Stable RequirementsUpfront planning is not wasted on changing scope
Regulatory RequirementsDocumentation and traceability are built-in
Fixed ContractsScope and price must be defined before work begins
Physical ConstructionSequential dependencies are inherent
Safety-Critical SystemsExtensive planning and testing are required
Low UncertaintyThe solution is known and proven

When to Consider Other Approaches

Predictive may not be ideal when:

  • Requirements are unclear or evolving
  • Customer feedback is needed throughout development
  • Time-to-market is critical
  • The team needs flexibility to adapt

Predictive vs. Adaptive Approaches

AspectPredictiveAdaptive (Agile)
PlanningUpfront, comprehensiveIterative, rolling wave
RequirementsFixed earlyEvolving throughout
DeliverablesAt end of projectIncrementally throughout
ChangeControlled, formal processExpected, embraced
Customer InvolvementAt milestonesContinuous
DocumentationExtensiveMinimal, sufficient

Key Takeaways

  • The predictive lifecycle follows a sequential, plan-driven approach
  • Five process groups organize project work: Initiating, Planning, Executing, Monitoring & Controlling, and Closing
  • Phase gates provide formal checkpoints for go/no-go decisions
  • Predictive works best when requirements are stable and well-understood
  • The project management plan integrates all subsidiary plans into a comprehensive roadmap
  • Approximately 40% of PMP exam content covers predictive approaches
Loading diagram...
Predictive Project Lifecycle Process Groups
Test Your Knowledge

What is the primary purpose of a phase gate (stage gate) in a predictive project?

A
B
C
D
Test Your Knowledge

Which process group typically requires the largest percentage of effort in a predictive project?

A
B
C
D
Test Your Knowledge

Predictive (waterfall) approaches are BEST suited for projects with which characteristic?

A
B
C
D