PM Portfolio — Iyahannah Wheeler

Project Charter — Enterprise Platform Migration

A comprehensive project charter for a cross-functional enterprise initiative

Scenario: Project charter for "Project Phoenix" (fictional) — migrating a Fortune 500 financial services company from a legacy on-premise CRM to a cloud-native SaaS platform. $4.2M budget, 18-month timeline, 3 business units, 5,000 end users.

Section 1 — Project Overview

Project Phoenix: Enterprise CRM Migration

◈ Business Case

Legacy CRM costs $2.8M/year in maintenance with 67% user satisfaction. Cloud migration will reduce TCO by 40%, improve user satisfaction to 85%+, and enable AI-powered analytics unavailable on the legacy platform. ROI breakeven at month 14.

◈ Scope

Migrate 12M+ customer records across 3 business units
Integrate with 8 downstream systems (ERP, billing, support)
Custom workflow automation for compliance (SOX, GLBA)
Train 5,000 end users across 14 office locations

◈ Success Criteria

100% data migration with zero data loss
85%+ user adoption within 90 days of go-live
< 2% increase in support tickets during transition
All compliance requirements maintained through cutover

◈ Constraints & Assumptions

No production downtime during peak trading hours (9am-4pm ET)
Regulatory freeze window: Nov 15 - Jan 15 (no deployments)
Assumes vendor provides dedicated migration engineering team
Budget contingency: 15% ($630K) held for risk mitigation

Section 2 — Governance & Stakeholders

Project Organization

Executive Sponsors

CTO — Final go/no-go authority
COO — Business readiness sign-off
CISO — Security & compliance approval

Steering Committee

VP Engineering — Technical delivery
VP Sales Operations — Sales BU readiness
VP Customer Service — Service BU readiness
Head of Compliance — Regulatory oversight

Key Milestones

Project Kickoff & Team OnboardingJan 15, 2026PM

Discovery & Requirements CompleteMar 1, 2026BA + Solutions Arch

Data Migration Test (Dry Run 1)May 15, 2026Data Eng

Integration Testing CompleteJul 30, 2026QA Lead

UAT Sign-off (All 3 BUs)Sep 15, 2026BU Leads

Pilot Launch (Sales BU)Oct 1, 2026PM + Sales VP

Full Production Go-LiveNov 10, 2026PM + CTO

Hypercare Complete & HandoffJan 10, 2027PM + Support

Section 3 — Budget Summary

Financial Overview

$4.2M

Total Budget

$1.8M

Platform License

$1.2M

Implementation

$570K

Change Mgmt

$630K

Contingency (15%)

Risk Register — Enterprise Migration Program

A structured risk register with severity scoring, likelihood assessment, and mitigation strategies

Framework: Risks scored on a 5x5 matrix (Impact x Likelihood). Severity = Impact × Likelihood. Critical (≥20), High (15-19), Medium (10-14), Low (<10). Reviews conducted bi-weekly at Steering Committee.

ID	Risk Description	Category	Impact	Likelihood	Severity	Mitigation Strategy	Owner	Status
R-001	Data migration causes record corruption or loss during transfer of 12M+ records	Technical	5	3	15 - High	Triple-validation checksums; 3 dry-run migrations before cutover; rollback scripts pre-staged; parallel running for 2 weeks post-migration	Data Eng Lead	Active
R-002	Regulatory freeze window (Nov-Jan) delays go-live if UAT slips	Schedule	5	4	20 - Critical	2-week schedule buffer before freeze; accelerated UAT track; pre-approved exception process for critical fixes during freeze	Program Manager	Escalated
R-003	User adoption below 85% target due to change resistance	People	4	3	12 - Medium	Champion network (25 power users); 6-week training program; gamified adoption tracking; exec-mandated transition deadline	Change Manager	Active
R-004	Third-party API integration failures with legacy ERP system	Technical	4	4	16 - High	API compatibility testing in sprint 2; middleware abstraction layer; fallback to batch file transfer if real-time sync fails	Integration Arch	Active
R-005	Budget overrun due to scope creep from BU-specific customization requests	Financial	3	4	12 - Medium	Change request board with ≥$25K approval threshold; bi-weekly scope review; 15% contingency reserved; MoSCoW prioritization for all CRs	Program Manager	Active
R-006	Key resource attrition — lead architect has competing project demands	Resource	4	2	8 - Low	Cross-training for backup resources; documented architecture decisions; escalation path to CTO for resource conflicts	Resource Mgr	Monitoring
R-007	CISO rejects security architecture during compliance review	Compliance	5	2	10 - Medium	Early engagement with InfoSec team in sprint 1; pre-approved security architecture template; SOC 2 Type II audit of vendor platform	Security Lead	Monitoring

Risk Heatmap Summary

Risk Distribution by Category

RAID Log — Program Governance Tracker

Risks, Assumptions, Issues, and Dependencies tracked across the full program lifecycle

Usage: Reviewed weekly at program standup. Items escalated to Steering Committee when severity exceeds threshold or when items are unresolved past their target date.

R-001

Data migration corruption during 12M record transfer

Triple-validation checksums and 3 dry-run migrations planned. Rollback scripts pre-staged.

OpenOwner: Data Eng LeadDue: May 15

R-002

Regulatory freeze window blocks November go-live

2-week buffer added. Accelerated UAT track approved by steering committee.

OpenOwner: Program ManagerDue: Sep 1

R-003

User adoption below 85% target

Champion network activated. Gamified adoption dashboard deployed.

MitigatedOwner: Change ManagerDue: Dec 15

A-001

Vendor will provide dedicated migration engineering team of 4 FTEs

Confirmed in SOW. Penalty clause if resources reduced below 3.

ValidatedOwner: Vendor Manager

A-002

Legacy system data is clean enough for automated migration

Data quality audit scheduled for sprint 2. Manual cleansing budget: $80K if needed.

UnvalidatedOwner: Data Eng LeadDue: Mar 15

A-003

All 3 BUs will release subject matter experts for UAT (2 weeks each)

Verbal agreement from BU leads. Written confirmation pending from Sales VP.

PendingOwner: Program ManagerDue: Jul 1

A-004

Current SOX compliance controls will map 1:1 to new platform

Compliance gap analysis in progress with internal audit team.

PendingOwner: Compliance LeadDue: Apr 1

A-005

Network bandwidth sufficient for cloud platform at all 14 locations

Network assessment scheduled. 3 remote offices flagged for potential upgrade.

UnvalidatedOwner: IT InfrastructureDue: Feb 28

I-001

Legacy API documentation is incomplete — 3 of 8 integrations undocumented

Reverse engineering in progress. Added 2 weeks to integration timeline. Escalated to CTO for original vendor support.

OpenOwner: Integration ArchDue: Mar 30

I-002

Sales BU requested 12 custom fields not in original requirements

Change request submitted ($45K impact). Approved by steering committee. Added to sprint 5.

ResolvedOwner: Business Analyst

I-003

Vendor SSO connector doesn't support client's MFA provider

Workaround identified: custom SAML bridge. Vendor committed to native support in Q3 release.

WorkaroundOwner: Security Lead

I-004

Testing environment provisioning delayed by 10 business days

Cloud provisioning bottleneck. Temporary shared environment approved. Dedicated env expected Apr 5.

OpenOwner: DevOps LeadDue: Apr 5

D-001

ERP team must complete API v3 upgrade before integration testing

ERP upgrade scheduled for May 1. Integration testing blocked until complete.

PendingOwner: ERP Program MgrDue: May 1

D-002

InfoSec must complete penetration testing before UAT

Pen test scheduled for Aug 1-15. Results needed for compliance sign-off.

ScheduledOwner: Security LeadDue: Aug 15

D-003

HR must approve overtime budget for go-live weekend support

Budget request submitted. Approval expected by Sep 1.

PendingOwner: HR Business PartnerDue: Sep 1

D-004

Change Advisory Board must approve production deployment

CAB submission requires 3-week lead time. Target submission: Oct 10.

Not StartedOwner: Release ManagerDue: Oct 10

D-005

Vendor must deliver custom reporting module by sprint 6

On track per SOW. Weekly check-ins with vendor PM.

On TrackOwner: Vendor ManagerDue: Jun 30

D-006

Training team must complete curriculum design before pilot launch

Curriculum draft 80% complete. Final review scheduled for Sep 15.

In ProgressOwner: Training LeadDue: Sep 25

Project Timeline — Gantt View

An 18-month program timeline with phase dependencies, milestones, and critical path highlights

Scenario: Project Phoenix timeline spanning Jan 2026 – Jun 2027. Four phases: Discovery, Build, Test & Validate, Deploy & Optimize. Critical path runs through data migration and integration testing.

Work Stream	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec	Jan	Feb	Mar
Discovery & Planning
Requirements Gathering
Architecture Design
◆ Requirements Sign-off
Build & Configure
Platform Configuration
Data Migration Dev
Integration Development
◆ Migration Dry Run 1
Test & Validate
Integration Testing
User Acceptance Testing
Security & Compliance Audit
◆ UAT Sign-off
Deploy & Optimize
Pilot Launch (Sales BU)
Full Go-Live
Hypercare & Optimization
◆ Project Close-out

Discovery & Planning

Build & Configure

Test & Validate

Deploy & Optimize

Milestone

Executive Status Report — Week 18

A weekly executive status report for steering committee review

Reporting Period: April 28 – May 2, 2026 | Phase: Build & Configure (Sprint 7 of 12) | Overall Status: Amber

Amber

Overall RAG

On Track

Budget

At Risk

Schedule

On Track

Quality

Accomplishments This Week

Data migration dry run #1 completed — 11.8M of 12.1M records migrated successfully (97.5%). 312K records flagged for manual review.

Integration with billing system (API v3) deployed to staging — All 47 test cases passing. Performance within SLA.

Champion network launched — 25 power users identified and enrolled. First training cohort begins next week.

SOX compliance mapping 80% complete — 48 of 60 controls mapped to new platform. 12 remaining in financial reporting module.

Planned Next Week

Resolve 312K flagged migration records — Data cleansing sprint. Target: reduce to <5K by Friday.

Begin ERP integration development — Dependent on ERP team completing API v3 upgrade (D-001).

Sprint 8 planning — Service BU workflows — Requirements finalized. Design review Thursday.

Security architecture review with CISO — Pre-read distributed. Meeting scheduled Wednesday 2pm.

Risks & Issues Requiring Attention

R-002 Escalated: ERP API upgrade delayed 2 weeks. If not resolved by May 15, integration testing shifts right, threatening Nov go-live. Action: CTO escalation meeting scheduled May 5.

I-004 Open: Testing environment still on shared infrastructure. Performance testing cannot begin until dedicated env provisioned. Expected: Apr 5.

New Risk: Vendor informed that custom reporting module may slip 2 weeks from Jun 30 to Jul 14 delivery. Monitoring impact on test schedule.

Decisions Needed from Steering Committee

1.

Approve accelerated UAT timeline to maintain November go-live date despite 2-week ERP delay. Requires BU leads to commit resources 2 weeks earlier than planned.

2.

Approve $45K change request for 12 additional custom fields requested by Sales BU. Within contingency budget.

3.

Confirm go/no-go criteria for pilot launch. Proposed: 95%+ data validation, 0 P1 defects, security audit passed, 3 BU sign-offs.

Program Progress

Overall Completion42% (Sprint 7/12)

Budget Consumed$1.68M / $4.2M (40%)

Risks Mitigated3 / 7 Active

Issues Resolved2 / 4 (50%)

PM Work Samples