Study guide
4.4 Planning & Managing Schedule
Project Management Professional PMP
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Introduction & Fundamentals
1.1 About the PMP Exam 1.2 What is a Project? 1.3 Project, Program & Portfolio Management 1.4 The Project Manager Role 1.5 PMBOK 7 Principles Overview 1.6 Performance Domains Overview 1.7 What Changed in the July 2026 PMP Exam
2 Chapter 2: People Domain Part 1
2.1 Managing Conflict 2.2 Leading a Team 2.3 Supporting Team Performance 2.4 Empowering Team Members 2.5 Training & Development 2.6 Building a Team 2.7 Removing Impediments
3 Chapter 3: People Domain Part 2
3.1 Negotiating Project Agreements 3.2 Collaborating with Stakeholders 3.3 Building Shared Understanding 3.4 Engaging Virtual Teams 3.5 Defining Team Ground Rules 3.6 Mentoring Stakeholders 3.7 Emotional Intelligence
4 Chapter 4: Process Domain - Planning
4.1 Determining Project Methodology 4.2 Integrating Project Planning 4.3 Planning & Managing Scope 4.4 Planning & Managing Schedule 4.5 Planning & Managing Budget 4.6 Planning & Managing Quality 4.7 Planning & Managing Resources 4.8 Planning & Managing Procurement
5 Chapter 5: Process Domain - Execution & Control
5.1 Executing with Urgency for Value 5.2 Managing Communications 5.3 Assessing & Managing Risks 5.4 Engaging Stakeholders 5.5 Managing Project Changes 5.6 Establishing Project Governance 5.7 Managing Project Issues 5.8 Managing Project Artifacts 5.9 Knowledge Transfer & Closure
6 Chapter 6: Business Environment Domain
6.1 Planning & Managing Compliance 6.2 Evaluating & Delivering Benefits 6.3 External Environment Changes 6.4 Supporting Organizational Change
7 Chapter 7: Agile & Hybrid Approaches
7.1 Agile Mindset & Values 7.2 Scrum Framework 7.3 Kanban & Lean 7.4 Extreme Programming (XP) 7.5 Hybrid Project Management 7.6 Agile Planning & Estimation 7.7 Agile Metrics & Tools
8 Chapter 8: Predictive (Waterfall) Approaches
8.1 Predictive Lifecycle 8.2 Scope Management 8.3 Schedule Management 8.4 Cost Management 8.5 Quality Management 8.6 Risk Management Process 8.7 Procurement & Contracts 8.8 Change Control
4.4 Planning & Managing Schedule
Key Takeaways Explain This Topic AI
The Critical Path Method (CPM) identifies the longest path through the project network, determining the minimum project duration
Activities on the critical path have zero float (slack), meaning any delay directly extends the project end date
The Precedence Diagramming Method (PDM) uses four relationship types: Finish-to-Start (most common), Start-to-Start, Finish-to-Finish, and Start-to-Finish (rare)
Schedule compression techniques include crashing (adding resources to critical path activities) and fast-tracking (performing activities in parallel that were planned sequentially)
Duration estimation techniques include analogous, parametric, three-point (PERT), and bottom-up estimating, with bottom-up being most accurate but time-consuming
Last updated: January 2026
Schedule management is about getting the project done on time. It involves defining activities, sequencing them, estimating durations, and developing a schedule that meets project objectives.
Schedule Management Processes
- Process Purpose Key Output
- Plan Schedule Management Establish policies and procedures for scheduling Schedule Management Plan
- Define Activities Identify specific actions to produce deliverables Activity List
- Sequence Activities Identify and document activity relationships Project Schedule Network Diagram
- Estimate Activity Durations Estimate work periods needed to complete activities Duration Estimates
- Develop Schedule Analyze sequences, durations, resources to create schedule Project Schedule
- Control Schedule Monitor status and manage schedule changes Schedule Forecasts
- Defining Activities
Activity Definition is the process of identifying and documenting the specific actions to be performed to produce the project deliverables.
Activity vs. Work Package
- Work Package (WBS) Activity (Schedule)
- Deliverable-oriented Action-oriented
- Noun (what we deliver) Verb (what we do)
- Example: "User Manual" Example: "Write User Manual"
- Lowest level of WBS Decomposed from work packages
- Activity Attributes
Each activity has attributes including:
- Activity ID and description
- Predecessor and successor activities
- Logical relationships
- Leads and lags
- Resource requirements
- Imposed dates
- Constraints and assumptions
- Sequencing Activities
Activity Sequencing determines the logical order in which activities should occur.
Precedence Diagramming Method (PDM)
PDM (also called Activity-on-Node) is the most common network diagramming technique. Activities are represented as nodes, and arrows show dependencies.
Dependency Types (Logical Relationships)
- Relationship Abbreviation Description Example
- Finish-to-Start FS Successor starts when predecessor finishes Foundation → Framing
- Start-to-Start SS Successor starts when predecessor starts Design → Documentation
- Finish-to-Finish FF Successor finishes when predecessor finishes Testing → Documentation
- Start-to-Finish SF Successor finishes when predecessor starts Rare - Just-in-time scenarios
Finish-to-Start (FS) is the most commonly used relationship.
Leads and Lags
Term Definition Example
Lead Amount of time successor can start before predecessor finishes FS-2 days: Painting can start 2 days before drywall finishes
Lag Amount of time successor must wait after predecessor finishes FS+3 days: Wait 3 days for concrete to cure before continuing
Dependency Categories
Category Description Can Change?
- Mandatory (Hard Logic) Inherent to the nature of work No
- Discretionary (Soft Logic) Based on best practices or preferences Yes
- External Involving non-project activities Usually No
- Internal Between project activities Sometimes
- Duration Estimation Techniques
- Comparison of Estimating Techniques
- Technique Accuracy Time Required When to Use
- Analogous Low (ROM) Quick Early estimates, limited data
- Parametric Moderate Moderate When historical data exists
- Three-Point (PERT) High Moderate Uncertainty exists
- Bottom-Up Highest Most Detailed planning phase
- Analogous Estimating
Uses historical data from similar activities or projects:
- Advantage : Quick and inexpensive
- Disadvantage : Less accurate, depends on similarity
- Best For : Early estimates when details are limited
- Parametric Estimating
Uses statistical relationships between historical data and variables:
- Example : Cost per square foot x total square feet
- Example : 2 hours per requirement x 50 requirements = 100 hours
- Advantage : More accurate than analogous when good data exists
- Disadvantage : Requires valid historical data and relationships
- Three-Point Estimating (PERT)
Uses three estimates to account for uncertainty:
- Estimate Symbol Description
- Optimistic O Best-case scenario (everything goes right)
- Most Likely M Most probable outcome
- Pessimistic P Worst-case scenario (everything goes wrong)
- Triangular Distribution : E = (O + M + P) / 3
- Beta Distribution (PERT) : E = (O + 4M + P) / 6
- Standard Deviation (Beta) : SD = (P - O) / 6
- Bottom-Up Estimating
Estimates individual activities and aggregates them:
- Advantage : Most accurate
- Disadvantage : Time-consuming and expensive
- Best For : Detailed estimates when WBS is complete
- Critical Path Method (CPM)
The Critical Path Method identifies the longest path through the project network, determining the minimum project duration.
Key Concepts
- Term Definition
- Critical Path Longest path through the network; determines project duration
- Float (Slack) Amount of time an activity can be delayed without delaying the project
- Total Float Time an activity can be delayed without delaying project end date
- Free Float Time an activity can be delayed without delaying any successor
- CPM Calculations
Forward Pass (calculates Early Start and Early Finish):
- ES = Earliest an activity can start
- EF = ES + Duration
Backward Pass (calculates Late Start and Late Finish):
- LF = Latest an activity can finish
- LS = LF - Duration
Float Calculation :
- Total Float = LS - ES = LF - EF
- Activities with zero float are on the critical path
Example Network Calculation Activity | Duration | ES | EF | LS | LF | Float | Critical?
- --------|----------|----|----|----|----|-------|----------
- A | 3 | 0 | 3 | 0 | 3 | 0 | Yes
- B | 4 | 3 | 7 | 4 | 8 | 1 | No
- C | 5 | 3 | 8 | 3 | 8 | 0 | Yes
- D | 2 | 8 | 10 | 8 | 10 | 0 | Yes
- Critical Path: A → C → D (Duration: 10 days)
- Schedule Compression
When the schedule must be shortened, use these techniques:
Crashing
Adding resources to critical path activities to reduce duration.
- Consideration Impact
- Added resources Increases cost
- Focus on Critical path activities only
- Diminishing returns Adding too many resources reduces effectiveness
- Trade-off Cost vs. time
- Fast-Tracking
Performing activities in parallel that were originally planned in sequence.
- Consideration Impact
- Parallel work May increase risk
- Focus on Activities that can safely overlap
- Requires Careful dependency analysis
- Trade-off Risk vs. time
- Comparison
- Technique Effect Cost Impact Risk Impact
- Crashing Reduce duration by adding resources Increases cost Minimal
- Fast-Tracking Reduce duration by overlapping activities Minimal cost increase Increases risk
- Schedule Presentation
- Gantt Charts
Gantt charts display activities as horizontal bars against a calendar:
- Shows activity start and end dates
- Displays task dependencies
- Easy to understand and communicate
- Can highlight critical path activities
- Milestone Charts
Show key dates and deliverables:
- High-level view for executives
- Focus on major achievements
- Simple and easy to communicate
- Network Diagrams
Show activity relationships and sequences:
- Precedence Diagramming Method (PDM)
- Useful for analyzing dependencies
- Required for CPM calculations
- Resource Optimization
- Resource Leveling
Adjusts the schedule based on resource constraints:
- May extend the critical path
- Resolves resource over-allocation
- Changes start and finish dates
- Resource Smoothing
Adjusts activities within their float to reduce resource peaks:
- Does not extend the critical path
- Works within existing schedule constraints
- May not fully resolve over-allocation
- Key Takeaways
- Activity definition identifies actions needed to produce deliverables
- PDM uses FS, SS, FF, and SF relationships to sequence activities
- Duration estimation ranges from quick analogous to detailed bottom-up
- Critical path is the longest path and determines project duration
- Float indicates schedule flexibility for non-critical activities
- Crashing adds resources; Fast-tracking overlaps activities