Primavera P6 Professional: Project Planning & Scheduling — Lesson 2: Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics

Learning Objectives

• Break down the roles, prerequisites, records, and decision points involved in Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics.
• Complete a controlled activity for Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics and capture logic-linked schedule and critical-path analysis.
• Challenge the result with a scenario involving mandatory constraints masking missing logic and creating an artificial completion date, then justify the corrective action.

Detailed Topics

• Activities
• Activity types
• Durations
• Milestones
• Relationships
• Lags
• Constraints
• Scheduling options
• Critical path
• Float
• And schedule diagnostics
• Decision ownership, prerequisites, and acceptance evidence for Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics
• Relevant access, data, integration, performance, recovery, and support considerations

Instructor Demonstration

The instructor configures and tests Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics within a scenario aimed at a logic-driven Primavera P6 schedule with controlled scope, realistic calendars and resources, defensible baselines, reliable updates, and decision-ready reporting. The walkthrough contrasts a valid setup with a flawed one and uses logic-linked schedule and critical-path analysis to make the difference explicit.

Hands-On Exercise

Complete a guided task covering Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics. After establishing a working baseline, reproduce “mandatory constraints masking missing logic and creating an artificial completion date,” isolate the responsible setting or data condition, apply a reversible fix, and update logic-linked schedule and critical-path analysis with before-and-after proof.

1. Record the starting state, assumptions, identities, data, and expected outcome.
2. Execute the planned workflow and collect evidence at each material checkpoint.
3. Test one valid path, one boundary condition, and the stated failure scenario.
4. Document the correction, retest result, rollback option, and follow-up owner.

Scenario Analysis

• Clarify the business trigger, affected roles, required records, and acceptable result for Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how logic-linked schedule and critical-path analysis should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Diagnose Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics by checking effective settings, ownership, source records, dependencies, and recent releases. Use logic-linked schedule and critical-path analysis to locate the earliest divergence. Treat “mandatory constraints masking missing logic and creating an artificial completion date” as a hypothesis until the same test passes after correction and still passes for a boundary case.

Validation Checklist

• Prerequisites and role permissions for Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics have been confirmed before execution.
• The result agrees with the expected values documented in logic-linked schedule and critical-path analysis.
• Exceptions are explained with evidence rather than hidden by manual correction.
• The final record names the approver, monitoring point, and next improvement action.

Lesson Outcome

Learners can apply Activities, activity types, durations, milestones, relationships, lags, constraints, scheduling options, critical path, float, and schedule diagnostics, explain the decisions made, and defend the result with logic-linked schedule and critical-path analysis.