SkarpChapter 9 of 20
Choosing and Tailoring Predictive Approaches
Not every plan-based project is the same; this module shows how predictive methods are selected and tailored to fit context, constraints, and organizational standards. You’ll practice thinking the way exam questions expect when they ask, “What should the project manager do next?” in a predictive setting.
Big Picture: When And Why Use Predictive
Why This Module Matters
You will learn how to recognize when a predictive life cycle fits best and how to tailor it. This is key to CAPM questions that ask: "What should the project manager do next?"
Predictive vs Adaptive
A predictive life cycle fixes scope, time, and cost early. An adaptive life cycle is agile or iterative, where detailed scope is defined and approved before each iteration.
Where Predictive Is Common
Predictive is frequent in construction, infrastructure, heavily regulated industries, and fixed-price contracts that demand clear scope, schedule, and cost upfront.
What You Will Practice
You will practice spotting predictive-friendly scenarios, tailoring artifacts like the WBS and baselines, understanding stage-gates, change control, and business analysis alignment.
Step 1: Recognize When Predictive Is a Good Fit
Spot the Predictive Scenario
Your first move in many questions is to detect when a predictive approach fits. Look for clear, stable requirements, heavy documentation, and formal approvals.
Stable Requirements
Predictive fits when requirements are well-understood and unlikely to change. Example: a standard warehouse using a proven design and building code.
Regulation and Compliance
Strong regulations (e.g., medical devices, aviation) push toward predictive approaches with detailed upfront design and documented approvals.
Cost of Change and Contracts
If late changes are very costly, or the contract is fixed-price with detailed deliverables and milestones, predictive planning and baselines are favored.
Step 2: Predictive vs Adaptive – Scenario Comparison
Scenario A: The Bridge
A city commissions a bridge under strict codes, fixed price, and schedule penalties. The firm has built many similar bridges using known methods.
Why Scenario A Is Predictive
Requirements and technology are stable; late changes are costly. This points to a predictive life cycle with detailed WBS, baselines, and formal change control.
Scenario B: The App
A startup builds a mobile app in a new market. Features change based on user feedback every few weeks. Learning and flexibility are key.
Why Scenario B Is Adaptive
Requirements evolve and changes are expected, so an adaptive life cycle with iterations and a prioritized backlog fits better than heavy upfront planning.
Step 3: Tailoring Predictive Processes and Artifacts
What Is Tailoring?
Tailoring means adjusting predictive processes and artifacts to the project’s size, complexity, and organizational standards instead of applying every tool at full strength.
Tailoring the Charter
A small internal project might use a short 2-page charter, while a large regulated project uses a detailed charter with formal signatures and regulatory references.
WBS and Work Packages
A work breakdown structure decomposes total scope. A work package is the lowest WBS level where cost and duration are estimated and managed.
Tailoring Baselines
Simple projects may use a basic Gantt with milestones; complex ones rely on detailed networks, critical path, and earned value to manage schedule and cost baselines.
Step 4: Tailoring Example – Same Method, Different Scale
Small Predictive Project
An office renovation (3 months, 5 people) uses a brief charter, a shallow WBS, a simple Gantt, a short risk list, and light but documented change control.
Large Predictive Project
A new manufacturing plant (3 years, hundreds of people) needs a detailed charter, deep WBS, complex schedule, extensive risk register, and strict change control.
Reading Exam Scenarios
Small, low-risk scenarios point to lightweight predictive tools. Large, complex, regulated scenarios call for formal, detailed planning and governance in your answer.
Step 5: Governance and Stage-Gate Reviews
What Is Governance?
Governance in predictive projects means formal oversight and decision-making, often through stage-gate reviews at key phase boundaries.
Typical Stages
Common stages: Concept/Feasibility, Planning/Design, Execution/Build, Testing/Validation, Handover/Closure, each ending with a review.
What Gates Decide
Stage-gates check deliverables, alignment with the business case, and whether risks, cost, and schedule are acceptable before approving the next phase.
Exam Signal
If a phase is complete and management must decide on next funding, the right move is usually a formal phase-end or stage-gate review, not jumping into the next phase.
Step 6: Baselines and Integrated Change Control
What Are Baselines?
Predictive projects fix scope, schedule, and cost baselines: the approved plans used to measure performance and control changes.
Integrated Change Control
Changes are requested, logged, impact-analyzed, then approved or rejected by the right authority before updating baselines and communicating.
Why Integrated?
A change in scope can affect schedule, cost, risk, and quality. Integrated change control checks all impacts before deciding.
Common Exam Traps
Beware answers that implement changes without analysis or approval, or that change schedule/cost without updating baselines and informing stakeholders.
Step 7: Predictive Projects and Business Analysis
Business Analysis in Predictive
In predictive projects, business analysis focuses on detailed upfront requirements, feeding into planning before execution begins.
Key BA Outputs
BA produces detailed requirements, specifications, acceptance criteria, and a requirements traceability matrix linking requirements to deliverables.
Link to Scope Management
The RTM helps ensure each requirement maps to a deliverable in the WBS and prevents extra, unapproved features from creeping in.
Exam Angle
When requirements are documented, the PM should use them to finalize WBS, estimates, baselines, RTM, and acceptance criteria before freezing the scope baseline.
Step 8: Thought Exercise – What Should the PM Do Next?
Use this thought exercise to practice CAPM-style reasoning.
Scenario 1
You are managing a predictive project to build a regional data center. The design phase is complete. All design documents have been approved by the regulatory authority. Senior management must decide whether to release funds for construction.
Question: What should the project manager do next?
Pause and think. Then check the guidance below.
Good next action:
- Prepare and conduct a formal phase-end (stage-gate) review with key stakeholders.
- Present completed design deliverables, updated risks, and refined cost and schedule estimates.
- Seek a decision on whether to proceed, adjust scope, or stop.
Scenario 2
You are leading a predictive software implementation. During testing, a stakeholder asks to add a "nice-to-have" reporting feature. The schedule baseline is tight, and there is no budget for extra work.
Question: What should the project manager do next?
Good next action:
- Ask the stakeholder to submit a formal change request.
- Log the request, analyze impacts on scope, schedule, cost, and risk.
- Present the analysis to the change authority (e.g., change control board) for a decision.
- Only implement the change if it is approved and baselines are updated.
Reflect: Did your instinct match the formal predictive approach (stage-gate, integrated change control), or did you jump to "just do it" or "just say no" without process?
Step 9: Quick Check – Choosing Predictive
Answer this CAPM-style question to test your understanding of when predictive fits best.
A project manager is assigned to deliver a new railway signaling system. National safety regulations strictly define performance requirements and documentation. The technology is mature and well understood. The client insists on a fixed-price contract and heavy penalties for late delivery. What is the MOST appropriate development life cycle?
- Adaptive life cycle with short iterations and evolving scope
- Predictive life cycle with detailed upfront planning and baselines
- No life cycle choice is needed; just begin work and adapt as issues arise
- Hybrid life cycle with minimal planning and mostly experimental work
Show Answer
Answer: B) Predictive life cycle with detailed upfront planning and baselines
The scenario shows stable, regulated requirements, mature technology, and a fixed-price contract with penalties. These factors favor a **predictive life cycle with detailed upfront planning and baselines**. Adaptive or mostly experimental approaches conflict with the client's need for predictability and regulatory compliance.
Step 10: Quick Check – Change Control and Tailoring
Test your understanding of integrated change control and tailoring in predictive projects.
On a small, low-risk predictive project, a stakeholder requests a minor scope change that will not affect the schedule or cost. What is the BEST action for the project manager?
- Implement the change immediately since there is no impact on schedule or cost
- Reject the change because the scope baseline was already approved
- Follow a simplified but documented change control process before updating the scope baseline
- Delay the decision until project closure to avoid disrupting the team
Show Answer
Answer: C) Follow a simplified but documented change control process before updating the scope baseline
Even on small projects, predictive approaches require **documented change control**. Tailoring allows a simplified process, but the PM should still log the change, confirm no impacts, obtain appropriate approval, and then update the scope baseline. Implementing changes without any process or rejecting all changes automatically are both poor practice.
Step 11: Flashcard Review – Core Predictive Terms
Flip through these cards to reinforce key definitions and concepts that frequently appear in predictive-project exam questions.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- work breakdown structure (WBS)
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- requirements traceability matrix (RTM)
- A grid that links product requirements from their origin to the deliverables that satisfy them.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- schedule variance
- A measure of schedule performance expressed as the difference between earned value and planned value.
- Stage-gate review
- A formal governance checkpoint at the end of a phase where stakeholders decide whether to continue, modify, or terminate the project based on predefined criteria.
- Integrated change control
- A process in predictive projects where all change requests are identified, documented, analyzed for impact on scope, schedule, cost, quality, resources, and risk, and then approved or rejected by the appropriate authority before updating baselines.
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- baseline
- The approved version of a work product, used as a basis for comparison to actual results, and changed only through formal change control procedures.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- work package
- The work defined at the lowest level of the work breakdown structure for which cost and duration are estimated and managed.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- schedule variance
- A measure of schedule performance expressed as the difference between earned value and planned value.
- stage-gate review
- A formal governance checkpoint at the end of a phase where stakeholders decide whether to continue, modify, or terminate the project based on predefined criteria.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- work breakdown structure
- A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
- integrated change control
- A coordinated process for reviewing, approving, and managing changes to project documents, deliverables, and baselines in a predictive project.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.