PROJECT CHARTER For Portal Migrations

PROJECT CHARTER for portal migrations
Risk management team:

Sanath Pabba - 500172953
Tarandeep singh dhunna - 500172262
Manpreet Verya - 500172442
Khushboo - 500173763
Upenderjit - 500173285
Version 1.6
September 22, 2019
For Internal Use Only Page 1

PROJECT CHARTER
Project Name: Project Number:

Migration of Websites from 2003 version PP00107923
to 2016/17
Date: 19 – 09 -2019 Revision Number: 1.6
1. PROJECT GOALS
The main purpose of the project is to upgrade the old traditional websites for ASIA,
RMS, Insight and Foresight application. At present the above website applications
are running on old environment with details:
Server : IIS 6.0
Visual Studio : 2003
Database: SQL Server 2003
and it will be upgraded to the latest tools like:
Server : IIS 9.0
Visual studio : 2016
Database : SQL Server 2018
2. DELIVERABLES
The below deliverables should be delivered as per the contract policy.

 Updated version and design functionality
 Knowledge transition documents with step by step approach
 Admin features will be provided on the sign-off.
 UI design will be completely new.
 Database will be shown as per the database team requirement.
 New solution will be provided in Repository.
3. SCOPE DEFINITION
As mentioned in deliverables the project is completely handed over once after successful
deployment. Regarding scope, it is clearly handed over in RFP document.
Below are including and excluding objects of the scope:

In Scope:
 KT docs will be provided
 Applications will be highly upgraded.
 Codes will be shared as per the policy
 Test reports will be handed over once after completion of manual testing.
 A warranty of 60 business days will be given as shadow support to rectify the issues
at conditional charges.
 The application will be tested in various levels like Dev, Pre-QA, QA, Pre-Prod, Prod.
Out of Scope:
 Database migration should be done from Client end.
 Project schedule won’t include client side testing.
 Our company won’t provide test cases for client side testing.
 Scheduled jobs will be taken care by IBM. Hence we won’t include Job Schedule
time.
4. PROJECT MILESTONES
 There will be multiple Phases of the project i.e. Analysis, Requirement classification,
coding phase, testing phase, warranty period.
 UI implementation
 C# integration
 Data base implementation, data mapping
 Job scheduling
 Testing – Manual and Automation.
5. ASSUMPTIONS, CONSTRAINTS & DEPENDENCIES
To implement above project we have lot many constraints and dependencies:

 User profiles should be created for team
 Environment set such as VM ware or virtual box should be given by client
 Once after successful installation of software’s only schedule will begin.
 All knowledge related documents should be handed over to team before
starting of analysis phase.
 Database migration is not considered under our scope, so the time will not be
considered. But buffer time will be considered.
 MOM will be shared to all stakeholders after every meeting.

6. RELATED DOCUMENTS
We are currently gathering our views and preparing the required documents.
Below documents will be shared from our end:
1) RFP
2) Resource sheet
3) Cost related document
4) Software’s list
We are expecting set of documents from client:
1) Run books
2) Reference documents
3) Business documents
4) Mapping sheets
5) Database schema
7. PROJECT ORGANIZATIONAL STRUCTURE
There are various stakeholders should be involved in the completion of project.

Function Name Role Company
Client POC Delivery
head
Client Technical
Architect contact
Vendor POC from
Manager vendor end
Job Scheduling IBM
scheduling manager
Software Software Capgemini
console team licensing
team
Server IT server Fujitsu
connectivity cons
team
Database Database CTS
administratio Management
n team team
Testing team Manual and NTT Data
automation
8. PROJECT AUTHORIZATION

Approved by: Business Manager Date
Anand Dharmadikari Amit sethi 21-09-2019

Approved by: Project Manager: Date
Tarandeep singh Manpreet singh 22-09-2019
9. Risks
There are few risks might face in the project implementation:

 Because of various levels of approvals the project sign off date may change.
 Since the coding standards are long back, we need architect approvals to make
obsolete codes with latest codes.
 Since there are lot of vendors are going to involve in the project (indirectly) the follow
ups should be done by client only.
 As the contract denoted for 2018 sql server will be the target but client is using 2019
version. Because of this there might be lot of discussions will be raised at client level
internally.
 Due to day light saving issues the application will make some sort of trouble with time
zone.
10. Timelines
The timeline will change as per the final contact policy conditions. But for fair explanation we
have provided the below time bounds.
Activity Start date End date

Analysis 26-09-2019 30-11-2019
Planning 01-12-2019 31-12-2019
Coding 01-01-2020 31-03-2020
Testing 01-04-2020 24-04-2020
Deployment Date 25-04-2020 26-04-2020
Warranty period 25/6 – 04- 2020 24-07-2020
Sign off date 28-07-2020 Not applicable

PROJECT CHARTER For Portal Migrations

Uploaded by

Copyright:

Available Formats

PROJECT CHARTER For Portal Migrations

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PROJECT CHARTER For Portal Migrations

Uploaded by

Copyright:

Available Formats

PROJECT CHARTER for portal migrations

Risk management team:

For Internal Use Only Page 1

Project Name: Project Number:

The below deliverables should be delivered as per the contract policy.

Below are including and excluding objects of the scope:

For Internal Use Only Page 2

5. ASSUMPTIONS, CONSTRAINTS & DEPENDENCIES

To implement above project we have lot many constraints and dependencies:

For Internal Use Only Page 3

7. PROJECT ORGANIZATIONAL STRUCTURE

There are various stakeholders should be involved in the completion of project.

For Internal Use Only Page 4

Anand Dharmadikari Amit sethi 21-09-2019

There are few risks might face in the project implementation:

Activity Start date End date

For Internal Use Only Page 5

You might also like