← PMP Exam Prep: Scope & Schedule

PMP Project Management Professional Exam Study Guide

Key concepts, definitions, and exam tips organized by topic.

33 cards covered

PMP Exam Prep: Scope & Schedule — Study Guide


Overview

This study guide covers the core concepts of project scope and schedule management as tested on the PMP exam, spanning both predictive (waterfall) and agile/hybrid frameworks. Topics include scope definition, WBS construction, schedule development, Critical Path Method (CPM) calculations, agile scheduling techniques, and Earned Value Management (EVM) for schedule control. Mastery of these areas is essential, as scope and schedule questions represent a significant portion of the PMP exam.


---


1. Scope Planning & Definition


Summary

Scope management begins in the Initiating process group and establishes the foundation for all project work. The key challenge is capturing what is included (and explicitly what is excluded) before any work begins. Poor scope definition is one of the leading causes of project failure.


Key Concepts


  • • Project Charter — The document that formally authorizes the project and grants the project manager authority to apply organizational resources. Created during Initiating; without it, the project has no formal standing.
  • • Project Scope Statement — The primary output of the Define Scope process. Describes deliverables, acceptance criteria, exclusions, assumptions, and constraints.
  • • Requirements Traceability Matrix (RTM) — Links each requirement to its business objective and traces it throughout the project lifecycle. Tracks status from inception to delivery.
  • • Product Scope vs. Project Scope

    • - Product Scope = Features and functions of the deliverable (measured against product requirements)

    - Project Scope = Work required to deliver the product (measured against the project management plan)


    Requirements Collection Techniques


    | Technique | Description |

    |---|---|

    | Delphi Technique | Experts submit ideas anonymously in multiple rounds until consensus is reached; reduces group bias |

    | Observation (Job Shadowing) | Watching users in their natural work environment; best when users can't articulate requirements |

    | Interviews | One-on-one or group conversations to elicit requirements directly |

    | Focus Groups | Facilitated discussion with a group of pre-qualified stakeholders |

    | Prototyping | Creating a working model to gather feedback before final design |


    Key Terms

  • • Acceptance Criteria — Conditions a deliverable must meet before stakeholder acceptance
  • • Assumptions — Factors believed to be true for planning purposes but not confirmed
  • • Constraints — Limitations on the project (time, cost, resources, etc.)
  • • Exclusions — Work explicitly outside the project scope

    • Watch Out For

    > ⚠️ Exam Trap: The Delphi Technique is anonymous — this is what distinguishes it from a regular expert judgment session. If a question mentions anonymity and consensus through rounds, the answer is Delphi.


    > ⚠️ Exam Trap: The Project Charter is created before detailed planning. You cannot create the scope statement without the charter first.


    ---


    2. Work Breakdown Structure (WBS)


    Summary

    The WBS is a hierarchical decomposition of all the work the project team must complete. It is one of the most critical planning tools in scope management, serving as the foundation for estimating cost, schedule, and resources.


    Key Concepts


  • • 100% Rule — The WBS must capture 100% of the scope defined in the project scope statement. Each child element must represent 100% of its parent's scope — no more, no less. Nothing is added; nothing is left out.
  • • Work Package — The lowest level of the WBS. The point at which cost and schedule can be reliably estimated and work can be assigned and managed.
  • • Control Account — A management control point above the work package level where scope, budget, and schedule are integrated and compared against Earned Value for performance measurement.
  • • WBS Dictionary — A companion document that provides detailed information about each WBS element (description, assigned resources, cost estimates, acceptance criteria, etc.).

    • Scope Control


  • • Scope Creep — Uncontrolled expansion of project scope without corresponding adjustments to time, cost, or resources. Prevented by the Control Scope process and formal Integrated Change Control.
  • • Validate Scope vs. Control Quality

    • | Process | Focus | Timing |

    |---|---|---|

    | Control Quality | Verifying deliverables meet quality standards | Before Validate Scope |

    | Validate Scope | Obtaining formal stakeholder acceptance | After quality checks pass |


    Key Terms

  • • Decomposition — The technique used to break down deliverables into smaller, manageable components
  • • Deliverable — Any unique, verifiable product, result, or capability
  • • Baseline — The approved version of the scope document; changes require formal change control

    • Watch Out For

    > ⚠️ Exam Trap: Control Quality comes before Validate Scope. You confirm the deliverable is correct before presenting it for acceptance. Many students confuse the order.


    > ⚠️ Exam Trap: The WBS contains deliverables, not activities. Activities are defined in the next process (Define Activities) when decomposing work packages further.


    ---


    3. Schedule Development


    Summary

    Schedule development is a multi-step process that transforms the WBS work packages into an actionable timeline. The PMP exam tests both the conceptual understanding of scheduling tools and the mathematical ability to apply them.


    Process Sequence

    ```

    Plan Schedule Management

    ↓

    Define Activities

    ↓

    Sequence Activities

    ↓

    Estimate Activity Durations

    ↓

    Develop Schedule

    ↓

    Control Schedule

    ```


    Dependency Types (Logical Relationships)


    | Type | Abbreviation | Meaning | Usage |

    |---|---|---|---|

    | Finish-to-Start | FS | B cannot start until A finishes | Most common |

    | Finish-to-Finish | FF | B cannot finish until A finishes | Common |

    | Start-to-Start | SS | B cannot start until A starts | Common |

    | Start-to-Finish | SF | B cannot finish until A starts | Rarely used |


    Lead and Lag


  • • Lag — A delay between predecessor and successor (e.g., FS + 2 days lag = successor starts 2 days after predecessor finishes)
  • • Lead — An acceleration (overlap) between predecessor and successor (e.g., FS – 2 days lead = successor starts 2 days before predecessor finishes)

    • Estimating Techniques


    #### Three-Point Estimating (PERT)


    $$\text{Expected Duration} = \frac{O + 4M + P}{6}$$


    $$\text{Standard Deviation} = \frac{P - O}{6}$$


  • • O = Optimistic estimate
  • • M = Most Likely estimate
  • • P = Pessimistic estimate

    • > Example: O = 4, M = 6, P = 14

    > Expected = (4 + 24 + 14) / 6 = 7 days

    > SD = (14 – 4) / 6 = 1.67 days


    Schedule Compression Techniques


    | Technique | Method | Cost Impact | Risk Impact |

    |---|---|---|---|

    | Crashing | Add resources to shorten duration | Increases cost | Lower risk than fast-tracking |

    | Fast-Tracking | Overlap sequential activities | Minimal direct cost | Increases rework risk |


    > Both techniques are applied to critical path activities only. Compressing non-critical path activities will not shorten the overall project.


    Resource Leveling

    Resource leveling adjusts activity start/finish dates to balance resource demand against availability. Applied when resources are over-allocated. Key consequence: often extends the project schedule.


    Key Terms

  • • Milestone — A significant point or event in the project; has zero duration
  • • Schedule Baseline — Approved schedule used to measure performance
  • • Network Diagram — Visual representation of activity sequences and dependencies

    • Watch Out For

    > ⚠️ Exam Trap: Resource leveling extends the schedule — it does not compress it. Do not confuse it with schedule compression techniques.


    > ⚠️ Exam Trap: PERT formula weights the Most Likely estimate by 4, making it the most influential factor. Know this formula cold.


    ---


    4. Critical Path Method (CPM)


    Summary

    The Critical Path Method is the most heavily tested quantitative topic in scope and schedule management. You must be able to perform forward pass, backward pass, and float calculations — and interpret what results mean for project management decisions.


    Core Definitions


  • • Critical Path — The longest path through the network diagram; determines the shortest possible project duration. Activities on the critical path have zero total float.
  • • Total Float (Slack) — How long an activity can be delayed without delaying the project end date
  • • Free Float — How long an activity can be delayed without delaying the early start of any successor activity

    • CPM Formulas


    | Metric | Formula |

    |---|---|

    | Early Finish (EF) | ES + Duration – 1 |

    | Late Start (LS) | LF – Duration + 1 |

    | Total Float | LS – ES or LF – EF |

    | Free Float | ES(successor) – EF(predecessor) – 1 |


    Forward Pass vs. Backward Pass


    | Pass | Direction | Calculates |

    |---|---|---|

    | Forward Pass | Left → Right | Early Start (ES) and Early Finish (EF) |

    | Backward Pass | Right → Left | Late Start (LS) and Late Finish (LF) |


    Interpreting Float Values


    | Float Value | Meaning |

    |---|---|

    | Zero float | Activity is on the critical path; any delay extends the project |

    | Positive float | Activity has schedule flexibility; not on critical path |

    | Negative float | Project is behind schedule; current plan cannot meet deadline — immediate corrective action needed |


    Near-Critical Path

    A path with very little float that is at risk of becoming the critical path. Monitoring near-critical paths helps anticipate schedule risks before they impact the project end date.


    Watch Out For

    > ⚠️ Exam Trap: The critical path is the longest path, not the shortest. It represents the minimum time to complete the project.


    > ⚠️ Exam Trap: Free Float is always ≤ Total Float. Free Float is the more restrictive of the two measures.


    > ⚠️ Exam Trap: Negative float does NOT mean you have extra time. It means the schedule is impossible as planned — action is required immediately.


    > ⚠️ Exam Trap: Crashing and fast-tracking are only effective on critical path activities. Applying them to activities with float will not shorten the overall schedule.


    ---


    5. Agile & Hybrid Scheduling


    Summary

    The PMP exam now heavily emphasizes agile and hybrid approaches. Agile scheduling replaces fixed long-range plans with iterative, adaptive cycles that deliver value incrementally. You must understand both the mechanics and the mindset.


    Core Agile Scheduling Concepts


  • • Sprint — A time-boxed iteration (typically 1–4 weeks) in Scrum during which a potentially shippable product increment is produced. Replaces traditional long-range scheduling with adaptive planning.
  • • Product Backlog — A prioritized list of features, requirements, and improvements. Owned and maintained by the Product Owner.
  • • Velocity — The average number of story points (work units) a team completes per sprint. Used to forecast how many sprints are needed to complete the remaining backlog.
  • • Burndown Chart — Tracks remaining work (story points or tasks) versus time. Shows whether the team is on track to complete work within the iteration or release.
  • • Definition of Done (DoD) — A shared team agreement on criteria that must be met before a backlog item is considered complete. Ensures transparency and consistency.

    • Rolling Wave Planning

    An iterative planning approach where:

  • • Near-term work is planned in detail
  • • Future work is planned at a high level
  • • Plans are progressively elaborated as more information becomes available

    • This bridges traditional and agile approaches and is relevant in both frameworks.


    Agile vs. Predictive Scheduling Comparison


    | Dimension | Predictive (Waterfall) | Agile (Scrum) |

    |---|---|---|

    | Planning Horizon | Full project upfront | Sprint-by-sprint |

    | Scope Flexibility | Fixed | Adaptive |

    | Schedule Unit | Gantt chart / milestones | Sprints / velocity |

    | Progress Tracking | % complete vs. baseline | Burndown chart |

    | Requirements Owner | Project Manager | Product Owner |


    Key Terms

  • • Sprint Review — End-of-sprint event where the team demonstrates the increment to stakeholders
  • • Sprint Retrospective — Team reflection on process improvements for the next sprint
  • • Story Points — Relative units of effort used to estimate backlog items
  • • Time-boxing — Fixing the duration of a sprint regardless of work completion status

    • Watch Out For

    > ⚠️ Exam Trap: In Scrum, the Product Owner manages the backlog, NOT the project manager or Scrum Master. Know who owns what.


    > ⚠️ Exam Trap: Velocity is used for forecasting, not for evaluating team performance or comparing teams. Do not confuse it with a productivity metric.


    > ⚠️ Exam Trap: Rolling wave planning is NOT exclusively agile — it is used in predictive projects as well when future work is uncertain.


    ---


    6. Schedule Control & Monitoring (EVM)


    Summary

    Earned Value Management (EVM) provides objective, quantitative measures of schedule and cost performance. The PMP exam requires you to calculate, interpret, and recommend actions based on EVM metrics.


    Key EVM Variables


    | Variable | Symbol | Definition |

    |---|---|---|

    | Planned Value | PV | Budgeted value of work scheduled to be done |

    | Earned Value | EV | Budgeted value of work actually completed |

    | Actual Cost | AC | Actual cost incurred for work performed |


    Schedule-Specific EVM Formulas


    | Metric | Formula | Interpretation |

    |---|---|---|

    | Schedule Variance (SV) | EV – PV | Negative = behind; Positive = ahead |

    | Schedule Performance Index (SPI) | EV / PV | < 1.0 = behind schedule; > 1.0 = ahead |


    > Example: EV = $85,000 | PV = $100,000

    > SV = 85,000 – 100,000 = –$15,000 (behind schedule)

    > SPI = 85,000 / 100,000 = 0.85 (getting $0.85 of work done per $1.00 planned)


    Schedule Baseline

  • • The approved version of the schedule model used to measure and monitor performance
  • • Can only be changed through the formal Integrated Change Control process
  • • Changes without approval = unauthorized scope/schedule creep

    • Watch Out For

    > ⚠️ Exam Trap: SV and SPI measure schedule performance in dollar terms, not time. A negative SV does not directly tell you how many days behind you are.


    > ⚠️ Exam Trap: SPI < 1.0 always means behind schedule, regardless of how close to 1.0 it appears. An SPI of 0.99 is still behind.


    > ⚠️ Exam Trap: The schedule baseline cannot be informally updated. Any change requires formal change control — this is a favorite scenario question on the exam.


    ---


    Quick Review Checklist


    Use this checklist in the final days before your exam to confirm mastery:


    Scope Management

  • • [ ] I can explain the purpose and content of the Project Charter and Project Scope Statement
  • • [ ] I know what the RTM tracks and why it matters
  • • [ ] I can distinguish between product scope and project scope
  • • [ ] I understand the 100% Rule and can apply it to WBS construction
  • • [ ] I know the difference between Work Packages and Control Accounts
  • • [ ] I can distinguish between Validate Scope and Control Quality (including their sequence)
  • • [ ] I can identify the Delphi Technique and Observation technique by their descriptions

    • Schedule Development

  • • [ ] I can recite the six schedule management processes in order
  • • [ ] I know all four dependency types (FS, FF, SS, SF) and can identify the most/least common
  • • [ ] I can define lead and lag and apply them to schedule scenarios
  • • [ ] I can apply the PERT formula (O + 4M + P) / 6 and calculate standard deviation
  • • [ ] I know the difference between crashing and fast-tracking (cost, risk, applicability)
  • • [ ]
    • 📝

    Take a Practice Test

    Test yourself with multiple choice questions
    📇

    Study with Flashcards

    Flip through all 33 cards

    Want more study tools?

    Subscribe for $7.99/mo and turn your own notes into personalized flashcards and study guides.

    View Pricing