Primavera P6 Professional Fundamentals Rel 21 — Lesson 2: Activities, Durations, Relationships, Constraints, Scheduling, and Float

Learning Objectives

• Explain the purpose and operating context of activity types, duration types, milestones, steps, and percent complete types.
• Apply relationships, lags, open ends, logic density, and sequencing and constraints, deadlines, calendars, schedule calculation, and critical path in a controlled environment.
• Validate outcomes and troubleshoot risks involving total float, free float, multiple paths awareness, and schedule-quality checks.

Detailed Topics

• activity types, duration types, milestones, steps, and percent complete types
• relationships, lags, open ends, logic density, and sequencing
• constraints, deadlines, calendars, schedule calculation, and critical path
• total float, free float, multiple paths awareness, and schedule-quality checks

Instructor Demonstration

Demonstrate activity types, duration types, milestones, steps, and percent complete types for a project schedule created from scope, baselined, statused, analyzed, and reported for stakeholder review; capture the exact configuration, code, command, transaction, query, dashboard, model, schedule, or report evidence that proves the expected result.

Hands-On Exercise

Complete a controlled Primavera P6 Professional Fundamentals Rel 21 exercise covering relationships, lags, open ends, logic density, and sequencing and constraints, deadlines, calendars, schedule calculation, and critical path; introduce an exception involving total float, free float, multiple paths awareness, and schedule-quality checks, diagnose it from evidence, apply the smallest reversible correction, and rerun acceptance checks.

1. Confirm scope, prerequisites, identities, dependencies, data, risks, and expected outcome.
2. Perform the course-specific configuration, development, administration, analysis, or business-process workflow.
3. Capture commands, settings, records, logs, screenshots, reports, metrics, or test results.
4. Compare the observed result with acceptance criteria and document corrective or preventive action.

Scenario Analysis

• Identify the technical or business decision and the stakeholders affected by it.
• Compare security, performance, reliability, compliance, cost, usability, and support trade-offs.
• Define rollback, recovery, communication, evidence, ownership, and escalation requirements.

Troubleshooting Guidance

Diagnose issues involving activity types, duration types, milestones, steps, and percent complete types, relationships, lags, open ends, logic density, and sequencing, constraints, deadlines, calendars, schedule calculation, and critical path, total float, free float, multiple paths awareness, and schedule-quality checks without making an unverified production change. Separate symptoms from causes, gather time-correlated evidence, test a reversible hypothesis, validate the correction, and record recurrence controls.

Validation Checklist

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

Lesson Outcome

Learners can apply Activities, Durations, Relationships, Constraints, Scheduling, and Float in a realistic Primavera P6 Professional Fundamentals Rel 21 scenario and defend the result with documented evidence.