Primavera P6 Fundamentals Rel 19 Ed 1 — Lesson 2: Activities, Durations, Relationships, Constraints, Scheduling, and Float

Learning Objectives

• Explain the architecture, workflow, or business purpose behind activity types, duration types, milestones, IDs, and steps.
• Apply finish-to-start, start-to-start, finish-to-finish, lags, and logic quality and constraints, deadlines, calendars, critical path, and total or free float in a controlled scenario.
• Validate outcomes and troubleshoot risks involving schedule calculation, out-of-sequence work awareness, checks, and narrative.

Detailed Topics

• activity types, duration types, milestones, IDs, and steps
• finish-to-start, start-to-start, finish-to-finish, lags, and logic quality
• constraints, deadlines, calendars, critical path, and total or free float
• schedule calculation, out-of-sequence work awareness, checks, and narrative

Instructor Demonstration

Demonstrate activity types, duration types, milestones, IDs, and steps within a construction project schedule created, baselined, updated, analyzed, and communicated through a reporting cycle, then capture the exact configuration, command, transaction, report, model, query, code, or process evidence that proves the result for lesson 2.

Hands-On Exercise

Implement a controlled exercise covering finish-to-start, start-to-start, finish-to-finish, lags, and logic quality and constraints, deadlines, calendars, critical path, and total or free float, then introduce and resolve an exception involving schedule calculation, out-of-sequence work awareness, checks, and narrative while preserving before-and-after evidence.

1. Confirm the environment, identities, inputs, dependencies, risks, and expected outcome.
2. Complete the course-specific configuration, development, analysis, or process workflow.
3. Capture settings, commands, data, outputs, logs, reports, screenshots, calculations, or test results.
4. Compare the observed result with acceptance criteria and document corrective action.

Scenario Analysis

• Identify the technical or business decision that must be made.
• Compare valid approaches and their security, performance, reliability, cost, compliance, and support trade-offs.
• Define rollback, recovery, ownership, communication, and evidence requirements.

Troubleshooting Guidance

Diagnose issues across activity types, duration types, milestones, IDs, and steps, finish-to-start, start-to-start, finish-to-finish, lags, and logic quality, constraints, deadlines, calendars, critical path, and total or free float, schedule calculation, out-of-sequence work awareness, checks, and narrative without making an unverified production change. Separate symptoms from causes, gather evidence, test the smallest reversible correction, rerun validation, and record preventive action.

Validation Checklist

• The requirement, scope, inputs, dependencies, and expected result are documented.
• The result is reproducible and supported by course-specific evidence.
• Normal, boundary, failure, security, performance, and operational conditions are reviewed.
• Exceptions, rollback, ownership, and the next improvement priority are recorded.

Lesson Outcome

Learners can apply Activities, Durations, Relationships, Constraints, Scheduling, and Float in a realistic Primavera P6 Fundamentals Rel 19 Ed 1 scenario and validate the result with documented evidence.