Primavera P6 Professional Fundamentals Rel 21 — Lesson 4: Statusing, Data Date, Progress, Variance, Layouts, Reports, and Closeout

Learning Objectives

• Explain the purpose and operating context of actual dates, remaining duration, units, percent complete, and data date.
• Apply schedule update, recalculation, out-of-sequence work, and forecast and filters, grouping, layouts, reports, printing, and stakeholder communication in a controlled environment.
• Validate outcomes and troubleshoot risks involving issue review, change control, archive, lessons learned, and scheduler handoff.

Detailed Topics

• actual dates, remaining duration, units, percent complete, and data date
• schedule update, recalculation, out-of-sequence work, and forecast
• filters, grouping, layouts, reports, printing, and stakeholder communication
• issue review, change control, archive, lessons learned, and scheduler handoff

Instructor Demonstration

Demonstrate actual dates, remaining duration, units, percent complete, and data date 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 schedule update, recalculation, out-of-sequence work, and forecast and filters, grouping, layouts, reports, printing, and stakeholder communication; introduce an exception involving issue review, change control, archive, lessons learned, and scheduler handoff, 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 actual dates, remaining duration, units, percent complete, and data date, schedule update, recalculation, out-of-sequence work, and forecast, filters, grouping, layouts, reports, printing, and stakeholder communication, issue review, change control, archive, lessons learned, and scheduler handoff 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 Statusing, Data Date, Progress, Variance, Layouts, Reports, and Closeout in a realistic Primavera P6 Professional Fundamentals Rel 21 scenario and defend the result with documented evidence.