Primavera P6 Professional Project Management Rel 19 Ed 1 — Lesson 2: WBS, Activities, Relationships, and Schedule Calculation

Technical Scope

• deliverable-oriented WBS and control-account structure
• activity types, durations, milestones, steps, and percent-complete types
• finish-start, start-start, finish-finish, lag, and logic quality
• schedule calculation, critical path, total float, constraints, and health review

Instructor Demonstration

The instructor will configure and verify deliverable-oriented WBS and control-account structure in the context of a new infrastructure project moving from enterprise setup through a controlled status cycle and stakeholder report. The demonstration captures commands, configuration, transactions, output, logs, plans, or screenshots that prove both the intended behavior and the control boundary.

Applied Workshop

Learners complete a controlled exercise covering activity types, durations, milestones, steps, and percent-complete types and finish-start, start-start, finish-finish, lag, and logic quality, then introduce a realistic exception involving schedule calculation, critical path, total float, constraints, and health review. They record assumptions, exact steps, expected and observed results, a reversible correction, and the evidence required for operational acceptance.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration, development, analysis, or business-process task.
3. Capture reproducible technical or transaction evidence and compare it with the expected value.
4. Explain the operational, security, performance, data-quality, or business trade-off.

Validation Standard

Acceptance for WBS, Activities, Relationships, and Schedule Calculation requires the result to be reproducible, traceable to approved inputs, consistent with the relevant Oracle or platform behavior, and supported by checks for security, data integrity, reliability, performance, and recoverability.

• The intended target, scope, and ownership are verified.
• Expected-value and negative-path checks pass.
• Security, reliability, performance, data quality, and support impacts are reviewed.
• Unexpected behavior is resolved before acceptance.

Failure Analysis

When the result differs from expectation, learners isolate the smallest proven cause across deliverable-oriented WBS and control-account structure, activity types, durations, milestones, steps, and percent-complete types, finish-start, start-start, finish-finish, lag, and logic quality; they avoid speculative production changes, preserve evidence, apply the lowest-risk correction, rerun the test, and document prevention.

Practical Outcome

Complete and defend a validated result for WBS, Activities, Relationships, and Schedule Calculation with a reusable implementation record or runbook.