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

Learning Objectives

• Assess the Oracle objects, services, calculations, reports, interfaces, or code involved in activities, durations, relationships, constraints, scheduling, and float.
• Operate a hands-on implementation or diagnostic sequence without bypassing governance or approvals.
• Resolve reproducibility by comparing expected and actual results and documenting corrective action.

Detailed Topics

• Activities
• Durations
• Relationships
• Constraints
• Scheduling
• Float
• requirements, ownership, prerequisites, data, and acceptance criteria for activities, durations, relationships, constraints, scheduling, and float
• security, controls, integration, performance, recovery, and support implications for activities, durations, relationships, constraints, scheduling, and float

Instructor Demonstration

Demonstrate activities, durations, relationships, constraints, scheduling, and float within a new project schedule created from scope definition through status updates, variance analysis, reporting, and controlled closeout. Use representative data and capture project and WBS records, activity logic, schedule output, resource assignments, baseline snapshots, progress updates, variance views, and management reports so another practitioner can independently verify the result.

Hands-On Exercise

Complete a controlled Primavera P6 Fundamentals Rel 21 Ed 1 exercise focused on activities, durations, relationships, constraints, scheduling, and float. Introduce one realistic failure involving incomplete scope, missing relationships, incorrect calendars, invalid constraints, resource conflicts, inaccurate updates, baseline misuse, and poor closeout records; isolate the cause, apply the smallest reversible correction, and rerun the acceptance checks.

1. Record the requirement, environment, identities, dependencies, data, controls, and expected result.
2. Perform the lesson workflow and capture evidence before and after each material change.
3. Test normal, boundary, failure, security, reconciliation, recovery, and operational conditions relevant to the topic.
4. Document the root cause, correction, rollback, owner, support action, and next improvement priority.

Scenario Analysis

• Map the end-to-end flow from source input through Oracle processing to the business output.
• Locate the control point where incorrect data, configuration, access, or integration could alter the result.
• Recommend preventive monitoring and an operational handoff with named ownership.

Troubleshooting Guidance

When activities, durations, relationships, constraints, scheduling, and float does not produce the expected result, confirm scope, effective dates, identities, data context, dependencies, and recent changes. Review the Oracle-specific logs, reports, traces, calculations, workflow history, transaction status, or diagnostic output relevant to the lesson. Test one reversible hypothesis at a time and verify that the correction does not create incomplete scope, missing relationships, incorrect calendars, invalid constraints, resource conflicts, inaccurate updates, baseline misuse, and poor closeout records elsewhere in the process.

Validation Checklist

• Prerequisites, ownership, data context, settings, and expected outcomes are documented.
• The workflow is reproducible and supported by project and WBS records, activity logic, schedule output, resource assignments, baseline snapshots, progress updates, variance views, and management reports.
• Security, controls, data quality, integration, performance, recovery, and support conditions are reviewed.
• Exceptions, corrective action, rollback, approvals, monitoring, and handover are recorded.

Lesson Outcome

Learners can apply Activities, Durations, Relationships, Constraints, Scheduling, and Float in a realistic Primavera P6 Fundamentals Rel 21 Ed 1 situation and defend the result with course-specific evidence.