Oracle Project Portfolio Mgmt Cloud Proj: Exec Mgmt Impl Ed 5 — Lesson 2: Work Plans, Tasks, Deliverables, and Progress Management

Technical Scope

• work-plan structures, tasks, milestones, dependencies, constraints, and schedules
• task assignments, effort, dates, baselines, percent complete, and progress collection
• deliverables, ownership, due dates, status, associations, and approval evidence
• schedule slippage, invalid dependencies, progress exceptions, and corrective planning

Instructor Demonstration

The instructor traces work-plan structures, tasks, milestones, dependencies, constraints, and schedules, then connects it to task assignments, effort, dates, baselines, percent complete, and progress collection. The demonstration captures the exact configuration, transaction, command, query, log, or screen evidence needed to prove intended behavior and the applicable control boundary.

Applied Workshop

Learners execute a guided lab focused on task assignments, effort, dates, baselines, percent complete, and progress collection and deliverables, ownership, due dates, status, associations, and approval evidence. The exercise introduces a realistic exception related to schedule slippage, invalid dependencies, progress exceptions, and corrective planning and requires a reversible correction supported by before-and-after evidence.

1. Confirm scope, identities, data, dependencies, controls, and expected result.
2. Perform the product-specific configuration or analysis and record exact steps.
3. Validate functional behavior, security, data integrity, and operational observability.
4. Introduce the defined failure condition, diagnose the cause, and apply a safe correction.
5. Document rollback, acceptance evidence, unresolved risk, and ownership.

Validation Standard

Acceptance requires accurate handling of deliverables, ownership, due dates, status, associations, and approval evidence, traceable proof for work-plan structures, tasks, milestones, dependencies, constraints, and schedules, and a repeatable recovery path for schedule slippage, invalid dependencies, progress exceptions, and corrective planning. Results must be understandable to both implementers and operational support teams.

Failure Analysis

Learners compare symptoms, logs, state, dependencies, and recent changes when schedule slippage, invalid dependencies, progress exceptions, and corrective planning occurs. The final diagnosis must separate the immediate fix from the preventive control.

Practical Outcome

The completed output is a tested work plans, tasks, deliverables, and progress management implementation or analysis, with validation evidence, troubleshooting notes, rollback guidance, and a concise operational handover.