Integrated Project Plan for Separation

Purpose

Create one authoritative roadmap that aligns every functional work-stream, external partner, and TSA dependency to a common timeline and critical path.

Core Components

• Master Work-Breakdown Structure (WBS) – Hierarchical list of all tasks, sub-tasks, and deliverables, each with unique ID and owner.
• Gantt-Style Timeline – Visual schedule showing task durations, start/finish dates, and dependencies.
• Critical-Path Analysis – Identification of tasks with zero float; any slip here delays Day 1.
• Resource Plan – Allocation of full-time equivalents, third-party hours, and budget by work-stream and month.
• Milestone Calendar – Key checkpoints such as mock cut-over, regulatory approvals, TSA exits, and Day 1 readiness gates.
• Risk & Issue Log – Central register with probability/impact scores, mitigation actions, and escalation status.
• Change-Control Register – Record of scope, schedule, or budget changes with approval history.

Step-by-Step Build Process

• Consolidate Work-Stream Plans
  • Collect detailed task lists from IT, Finance, HR, Legal, Operations, Supply Chain, and TSA owners.
  • Align task naming conventions and coding structures for easy roll-up.
• Sequence and Link Dependencies
  • Use predecessor–successor logic to connect tasks (e.g., “ERP data migration” precedes “finance opening balances”).
  • Highlight cross-functional dependencies in red for weekly review.
• Assign Ownership and Effort
  • Every task gets a single accountable owner and estimated hours or cost.
  • Load resource constraints to flag over-allocations early.
• Validate Critical Path
  • Run scheduling software to identify zero-slack activities.
  • Present critical path to Steering Committee; secure commitment to protect those tasks from scope creep.
• Set Baseline
  • Freeze task dates, budgets, and scope once approved by the PMO and Steering Committee.
  • Use this baseline for variance tracking.
• Establish Reporting Cadence
  • Weekly work-stream status reports rolled into a PMO dashboard.
  • RAG (Red/Amber/Green) status for schedule, budget, scope, and risk at both work-stream and programme level.
• Integrate TSA Exit Milestones
  • Insert TSA sunset dates and exit-readiness checkpoints directly into the master plan.
  • Link replacement-system build tasks to corresponding TSA exit milestones.

Governance and Control

• Weekly PMO Review – Focus on schedule variance, critical-path tasks due in next 14 days, and new risks/issues.
• Monthly Steering-Committee Meeting – Approve major changes, unblock escalated issues, and review budget burn.
• Change-Control Thresholds – Any variance > ±5 % schedule or budget requires Steering-Committee approval.

Deliverables

• Integrated project-plan file (MS Project or equivalent) with resource, cost, and baseline data.
• Critical-path snapshot and narrative summary for executive communication.
• RAG dashboard with earned-value metrics (planned vs. actual work and cost).
• Updated risk, issue, and change-control logs.

Common Pitfalls to Avoid

• Allowing each function to manage its own plan in isolation—leads to missed cross-dependencies.
• Ignoring resource constraints—people double-booked across work-streams create hidden delays.
• Updating schedules informally—changes outside the change-control process erode baseline integrity.
• Failing to integrate TSA exit milestones—services linger, costs balloon, and independence slips.

A comprehensive, enforced integrated project plan keeps every team marching in lockstep toward a seamless Day 1 and an on-time TSA exit.