You are on page 1of 10

Platform SAMPLE Project Plan (version 7.2.

2 and above) Responsibility


NOTE: This project plan is for Pega platform version 7.2.2 and higher. If your
system is running on a lower version of the Pega platform, contact your Pega
modernization specialist for guidance.

Phase 1: Assessment and Planning


Complete the Cloud Migration Gap Assessment Worksheet Client
Run the Pega Modernization Tool provided by Pega Client
Review the Modernization Tool output report with the Pega team Pega/Client
Client
Identify gaps/issues between the existing system and Pega Cloud requirements
Document use cases, requirements, and solutions for all identified gaps. Client
Create a plan to remediate all identified gaps/issues, such as those related to: Client

Updating (updating tables, converting Flow Actions, resolving rule conflicts, Client
etc.)
Post Update Tasks (OOTB Rule Override Issues, Application Validation Issues, Client
etc.)
Cloud Migration (Converting database views to report definitions, etc.) Client
Integration (SSO, third party integration points, etc.) Client
Modernization (stage based case management, Data Pages, Guardrail Client
warnings related to Security or performance)
Define a data archive/purge strategy Client
Define a data migration strategy for each environment Client
If development continues on the existing system after the initial migration, plan Client
how and when to move the new development to Pega Cloud
Define a Testing Strategy Pega/Client
Plan how to connect between existing systems and Pega Cloud Pega/Client
Create project plan Client
Establish project governance and cadence Pega/Client

Client
NOTE: Pega recommends beginning the process of setting up connectivity to Pega
Cloud as soon as possible, so that the network and security approvals do not
delay the project.

Phase 2: Application Migration, Update, and Remediation


Prepare Pega Cloud Dev Environment
Pega provides access to client environments on Pega Cloud Pega
Migrate Application Code and Associated Data via RAP from existing systems to Client
Pega Cloud Development Environment
Establish connectivity to Pega Cloud Pega/Client
Migrate any other application configuration from old environment to new (SSO, Client
DNS entries, external DB connectivity, Configuration files)
Remediate Application Gaps in Pega Cloud Development Environment
Remediate all gaps/issues identified during planning Client
Review the applications using PDC Pega/Client
Test the application, including regression testing Client
Fix any issues found in testing Client
Sign off on development environment Update, Migration, and Modernization Client
remediation and testing

Phase 3: Validating Applications in Pega Cloud


QA/Test Environment Migration
Promote Rules from Pega Cloud Dev environment. Client
Client
Migrate any other application configuration via RAP from source environment to
QA/Test (SSO, DNS entries, external DB connectivity, Configuration files)
Import any test data from source QA environment using RAP files. Client
Review the applications using PDC Pega/Client
Client
Perform end-to-end application functional testing, including integration testing.
Fix any issues found in testing Client
Signoff on QA Migration and Testing Client

Staging Environment Migration


Promote Rules from QA environment to Cloud Staging Client
Migrate any other application configuration from old environment to Staging Client
(SSO, DNS entries, external DB connectivity, Configuration files)
Complete pre-requisites for data migration of staging environment Pega/Client
Provision data migration tooling environments in Pega Cloud Pega
Migrate data from source system to Pega Cloud using data migration tooling Pega/Client
Perform data only update on Pega Cloud staging environment Pega
Restore Custom System name & PDC URL (if required) Client
Review the applications using PDC Pega/Client
Raise a ticket to request Pen testing Client
Test, including regression/integration/Pen testing Client
Fix any issues found in testing Client
Signoff on Staging Migration and Testing Client

Phase 4: Data Migration and Go-Live


Perform Dry Run Migration

NOTE: Create a Runbook throughout this process. Client

Disable agents, listeners, etc. on Pega Cloud production environment Client


Migrate Application Code from Staging to Pega Cloud Production Client/Pega
Clone the source production environment (read-only) Client
Complete pre-requisites for data migration of prod environment Pega/Client
Migrate data from source system to Pega Cloud using data migration tooling Pega/Client
Perform data only update on Pega Cloud production environment Pega
Restore Custom System name & PDC URL (if required) Client
Review the applications using PDC Pega/Client
Sanity test the applications Client
Run performance tests Client
Run security tests (if not completed in staging environment) Client
Remediate any issues Client
Signoff on Dry Run Migration and Testing Client

Production Data Migration and Go-Live


Submit request for data migration Client
Follow the steps laid out in the Runbook Pega/Client
Have on-line bridge calls with the Pega team Pega/Client
Have Go/No-go decision meeting with all stakeholders Pega/Client
When Migration is completed, direct users to new URLs Client

Post Go-Live Support (HyperCare)


Pega monitors the Pega Cloud deployment Pega
Review what went well and what could be improved in the future Pega/Client
Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10Week 11Week 12

x
x
x

x x
x x

x x

x x

x x
x x
x x

x x
x
x

x
x
x
x
x

x
x

x
x x x
x
x x
x x

x
x
x

x
x
x

x
x
x
x
x
x
x
x
x x
x x
x

x
x
x
x
x
x
x
x
Week 13 Week 14 Week 15
x
x
x
x x
x

x
x
x
x
x

x
x
The sample project plan includes color-
coding to help track the progress of the
migration.
Enter the letter in a cell, then tab out of
the cell to add the color coding

Letter Color Meaning


x x Not started
a a At risk or delayed
b b Blocked
c c Completed

You might also like