Schedule Analysis: Conflict Identification and Resource Leveling
PMBOK v8 Definition
The schedule is analyzed to identify conflicts with logical relationships and to determine if resource leveling is required before the schedule is approved and used as a baseline. This analysis occurs after activity start and end dates are set, and project team members review their assignments to confirm that dates do not conflict with resource calendars or assigned activities in other projects or tasks. This activity belongs to the Schedule Management knowledge area within the Planning process group, specifically during the Develop Schedule process.
Why It Matters for the Exam
PMI exam questions frequently test the sequence and decision points in schedule development—specifically when resource leveling becomes necessary. Questions appear as situational scenarios where you must identify the correct next step after a draft schedule reveals resource conflicts, or as definition-based questions asking what triggers resource leveling before baseline approval.
Key Points to Remember (for the exam)
- Critical Sequence: Set start/end dates → Team reviews assignments → Analyze logical relationship conflicts → Determine if resource leveling is needed → Approve schedule as baseline
- Resource Leveling Trigger: Required when resource calendars conflict with assigned activities or when logical relationships show resource overallocation
- Draft Schedule Purpose: Provides information about what work should be done and in what sequence deliverables should be accomplished
- Team Review: Team members must confirm that start and end dates do not conflict with resource calendars or assigned activities in other projects/tasks
- Baseline Approval: The schedule cannot be approved and used as a baseline until resource leveling requirements are determined and addressed
- Logical Relationships: Every work package and activity (except first and last) must connect to at least one predecessor and one successor with appropriate logical relationships
- Lead/Lag: May be necessary to use lead or lag time between activities to support a realistic and achievable project schedule
Typical PMI Exam Example
Situation: A project manager has developed a draft schedule with start and end dates for all activities. During team review, two team members assigned to different activities discover they are both scheduled for the same critical resource during overlapping timeframes.
Question: What should the project manager do NEXT?
Correct answer: Analyze the schedule to identify conflicts with logical relationships and determine if resource leveling is required before the schedule is approved and used as a baseline.
PMI Exam Traps
- Trap: Confusing resource leveling with resource smoothing → Reality: Resource leveling changes the project end date; resource smoothing adjusts within float without changing the end date. This analysis determines IF leveling is needed before baseline approval.
- Trap: Thinking schedule baseline approval happens before resource conflict analysis → Reality: The schedule must be analyzed for logical relationship conflicts and resource leveling requirements BEFORE it is approved and used as a baseline.
- Trap: Assuming team member review is optional → Reality: Team members assigned to activities MUST review their assignments and confirm that start and end dates do not conflict with resource calendars or assigned activities in other projects or tasks.
- Trap: Believing logical relationships are fixed once defined → Reality: Logical relationships may require adjustment after resource analysis to create a realistic project schedule, and lead/lag time may be needed.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Schedule Baseline | Output of this analysis | Baseline updates occur when significant changes affect project timing; must be formally integrated |
| Resource Calendars | Input to schedule analysis | Team members confirm dates do not conflict with resource calendars or other project assignments |
| Logical Relationships | Core concept being analyzed | Every activity (except first/last) must have at least one predecessor and one successor |
| Monitor and Control Schedule | Subsequent process | After baseline approval, monitor status, update schedule, and manage changes to agreed-upon schedule |
Quick Review Questions
- What must occur BEFORE a schedule can be approved and used as a baseline?
- Who should review the start and end dates of activities after they are set?
- What are the two types of conflicts that schedule analysis examines?
- What is the minimum number of predecessors and successors required for each activity (except first and last)?
- Why might lead or lag time be necessary between activities?
PMBOK v8 Reference
Section 2.3.2.2 - Develop Schedule (Planning Process Group, Schedule Management Knowledge Area)
The schedule is analyzed to identify conflicts with logical relationships and to determine if resource leveling is required before the schedule is approved and used as a baseline. This section also covers the team review process where assigned team members confirm that start and end dates do not conflict with resource calendars or assigned activities in other projects or tasks.