Cloud based ERP system implementation in Wiser - Project Charter
VerifiedAdded on 2023/06/11
|13
|3588
|211
AI Summary
This project charter outlines the implementation of a cloud based ERP system in Wiser, a UK based employment service provider company. The project aims to increase overall business efficiency and resolve operational and functional issues. The estimated cost is £80,000 and completion time is 180 days.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
Project Charter Document
Project Name: Cloud based ERP system implementation in Wiser
Department: <Please fill>
Focus Area: ERP system implementation and its application in the business
organization
Product/Process: Cloud based ERP system
Prepared By
Document Owner(s) Project/Organization Role
Project Charter Version Control
Version Date Author Change Description
[Replace this text
with the name of
the Document
Owner.]
Document created
[Replace this text
with the name of
the Change
Owner.]
[Replace this text with a list of changes for
this Owner on this Date and Version.]
[Change 1]
[Change 2]
[Change n]
Confidential
6977524687867803901.docx
Last printed on 3/23/2004 11:48:00 AM
Project Name: Cloud based ERP system implementation in Wiser
Department: <Please fill>
Focus Area: ERP system implementation and its application in the business
organization
Product/Process: Cloud based ERP system
Prepared By
Document Owner(s) Project/Organization Role
Project Charter Version Control
Version Date Author Change Description
[Replace this text
with the name of
the Document
Owner.]
Document created
[Replace this text
with the name of
the Change
Owner.]
[Replace this text with a list of changes for
this Owner on this Date and Version.]
[Change 1]
[Change 2]
[Change n]
Confidential
6977524687867803901.docx
Last printed on 3/23/2004 11:48:00 AM
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Project Charter
TABLE OF CONTENTS
1 PROJECT CHARTER PURPOSE.......................................................................................... 3
2 PROJECT EXECUTIVE SUMMARY.......................................................................................3
3 PROJECT OVERVIEW........................................................................................................... 3
4 PROJECT SCOPE.................................................................................................................. 3
4.1 Goals and Objectives................................................................................................. 3
4.2 Departmental Statements of Work (SOW)..................................................................4
4.3 Organizational Impacts............................................................................................... 4
4.4 Project Deliverables.................................................................................................... 4
4.5 Deliverables Out of Scope.......................................................................................... 4
4.6 Project Estimated Costs & Duration...........................................................................4
5 PROJECT CONDITIONS........................................................................................................ 5
5.1 Project Assumptions................................................................................................... 5
5.2 Project Issues............................................................................................................. 5
5.3 Project Risks.............................................................................................................. 5
5.4 Project Constraints..................................................................................................... 5
6 PROJECT STRUCTURE APPROACH...................................................................................6
7 PROJECT TEAM ORGANIZATION PLANS...........................................................................6
8 PROJECT REFERENCES...................................................................................................... 6
9 APPROVALS.......................................................................................................................... 6
10 APPENDICES......................................................................................................................... 8
10.1 Document Guidelines................................................................................................. 8
10.2 Project Charter Document Sections Omitted..............................................................8
Confidential Page 2 8/29/2024
TABLE OF CONTENTS
1 PROJECT CHARTER PURPOSE.......................................................................................... 3
2 PROJECT EXECUTIVE SUMMARY.......................................................................................3
3 PROJECT OVERVIEW........................................................................................................... 3
4 PROJECT SCOPE.................................................................................................................. 3
4.1 Goals and Objectives................................................................................................. 3
4.2 Departmental Statements of Work (SOW)..................................................................4
4.3 Organizational Impacts............................................................................................... 4
4.4 Project Deliverables.................................................................................................... 4
4.5 Deliverables Out of Scope.......................................................................................... 4
4.6 Project Estimated Costs & Duration...........................................................................4
5 PROJECT CONDITIONS........................................................................................................ 5
5.1 Project Assumptions................................................................................................... 5
5.2 Project Issues............................................................................................................. 5
5.3 Project Risks.............................................................................................................. 5
5.4 Project Constraints..................................................................................................... 5
6 PROJECT STRUCTURE APPROACH...................................................................................6
7 PROJECT TEAM ORGANIZATION PLANS...........................................................................6
8 PROJECT REFERENCES...................................................................................................... 6
9 APPROVALS.......................................................................................................................... 6
10 APPENDICES......................................................................................................................... 8
10.1 Document Guidelines................................................................................................. 8
10.2 Project Charter Document Sections Omitted..............................................................8
Confidential Page 2 8/29/2024
Project Charter
1 PROJECT CHARTER PURPOSE
The following report reflects on the development of cloud based ERP in
wiser, which is an UK based organization.
2 PROJECT EXECUTIVE SUMMARY
This project depicts the role of ERP system in the business organization and the way through
which it can enhance the overall business efficiency simultaneously. After analyzing the details of
the cloud based ERP system, it is defined that for successful accomplishment of the solution
around 180 days and £80,000 will be required and the project phase considered for the ERP
development are divided into five work packages in terms of project initiation, planning,
development, testing and closure.
The objectives of the project are as follows:
To identify the current issues facing by Wiser
To select the most suitable cloud vendor for Wiser
To implement cloud based ERP solution within 180 days and £80,000
The goal of the project is to develop cloud based ERP solution for the business organization
named as Wiser to increase its overall business efficiency.
The scope of the project is to build an accurate cloud based ERP platform for Wiser to resolve
their operational and functional issues.
The project is assumed to be completed in 180 days within an estimated budget of £80,000.
Wiser was facing many issues associated to security, availability, support, scalability and
resources. With the incorporation of cloud based ERP these risks will be completely
resolved.
The total cost estimated for the successful implementation of the cloud based ERP is
£80,000
In Wiser the cloud based ERP implementation will take around 180 days.
Wiser a United Kingdom based company serves in-house creative as well as recruitment
solution for the applied candidates. The company is responsible to build employer brands
for attracting amazing people an guide the candidates to serve them a dream career.
3 PROJECT OVERVIEW
Wiser is a known United Kingdom based employment service provider Company. The services
offered by the company is mail y developed to attract the consumers. Besides candidates and
applicants Wiser also has guides who can guide the candidates and act as mentors so that they
can build their professional career successfully. However, due to lack of functional and
operational activities Wiser fails to store their information. In order to resolve the issues of manual
data management system the company is willing to implement cloud based ERP solution to store
and access different information with high security.
Confidential Page 3 8/29/2024
1 PROJECT CHARTER PURPOSE
The following report reflects on the development of cloud based ERP in
wiser, which is an UK based organization.
2 PROJECT EXECUTIVE SUMMARY
This project depicts the role of ERP system in the business organization and the way through
which it can enhance the overall business efficiency simultaneously. After analyzing the details of
the cloud based ERP system, it is defined that for successful accomplishment of the solution
around 180 days and £80,000 will be required and the project phase considered for the ERP
development are divided into five work packages in terms of project initiation, planning,
development, testing and closure.
The objectives of the project are as follows:
To identify the current issues facing by Wiser
To select the most suitable cloud vendor for Wiser
To implement cloud based ERP solution within 180 days and £80,000
The goal of the project is to develop cloud based ERP solution for the business organization
named as Wiser to increase its overall business efficiency.
The scope of the project is to build an accurate cloud based ERP platform for Wiser to resolve
their operational and functional issues.
The project is assumed to be completed in 180 days within an estimated budget of £80,000.
Wiser was facing many issues associated to security, availability, support, scalability and
resources. With the incorporation of cloud based ERP these risks will be completely
resolved.
The total cost estimated for the successful implementation of the cloud based ERP is
£80,000
In Wiser the cloud based ERP implementation will take around 180 days.
Wiser a United Kingdom based company serves in-house creative as well as recruitment
solution for the applied candidates. The company is responsible to build employer brands
for attracting amazing people an guide the candidates to serve them a dream career.
3 PROJECT OVERVIEW
Wiser is a known United Kingdom based employment service provider Company. The services
offered by the company is mail y developed to attract the consumers. Besides candidates and
applicants Wiser also has guides who can guide the candidates and act as mentors so that they
can build their professional career successfully. However, due to lack of functional and
operational activities Wiser fails to store their information. In order to resolve the issues of manual
data management system the company is willing to implement cloud based ERP solution to store
and access different information with high security.
Confidential Page 3 8/29/2024
Project Charter
4 PROJECT SCOPE
4.1 Goals and Objectives
Goals Objectives
The cloud based system
will increase the overall
business efficiency
The system will be
secured enough and the
cost and time estimated
for the system
implementation is also
reasonable
To consider each necessary factors of cost and timeline
Another objective of the project developer is to complete the
project within £80,000 with a time specification of 180 days
or (6 months).
4.2 Departmental Statements of Work (SOW)
Departmental SOW Owner/Prime Due Date/Sequence
A project change request Project manager Fri 6/1/18- Tue 6/12/18
Requesting the cloud vendor Cloud vendor provider Mon 7/23/18-Thu 7/26/18
Submission of final design
interface
Project sponsor and project
manager
Wed 10/3/18-Wed 1/30/19
4.3 Organizational Impacts
Organization
Impact to and Participation of
Organization
Wiser The company is a home for the young
generation who dream bigger and whose
level of expectation is more than the
general one. This employment
environment gives creative, recruitment
meets for building and transforming
employer brand.
The creativity of Wiser innovate with
design, web as well as film for capturing all
those factors that the company makes. The
recruiters associated to the company are
much professional and thus introduces the
companies with the most appropriate,
suitable and eligible candidate.
The company is willing to implement cloud
based ERP solution for in increasing their
overall business efficiency, operational and
functional practices.
Confidential Page 4 8/29/2024
4 PROJECT SCOPE
4.1 Goals and Objectives
Goals Objectives
The cloud based system
will increase the overall
business efficiency
The system will be
secured enough and the
cost and time estimated
for the system
implementation is also
reasonable
To consider each necessary factors of cost and timeline
Another objective of the project developer is to complete the
project within £80,000 with a time specification of 180 days
or (6 months).
4.2 Departmental Statements of Work (SOW)
Departmental SOW Owner/Prime Due Date/Sequence
A project change request Project manager Fri 6/1/18- Tue 6/12/18
Requesting the cloud vendor Cloud vendor provider Mon 7/23/18-Thu 7/26/18
Submission of final design
interface
Project sponsor and project
manager
Wed 10/3/18-Wed 1/30/19
4.3 Organizational Impacts
Organization
Impact to and Participation of
Organization
Wiser The company is a home for the young
generation who dream bigger and whose
level of expectation is more than the
general one. This employment
environment gives creative, recruitment
meets for building and transforming
employer brand.
The creativity of Wiser innovate with
design, web as well as film for capturing all
those factors that the company makes. The
recruiters associated to the company are
much professional and thus introduces the
companies with the most appropriate,
suitable and eligible candidate.
The company is willing to implement cloud
based ERP solution for in increasing their
overall business efficiency, operational and
functional practices.
Confidential Page 4 8/29/2024
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Project Charter
4.4 Project Deliverables
Milestone Deliverable
1. Project initiation phase
2. Project planning
phase
Defining project scope and company background
Identification of project team
Stakeholders identification for the business blueprint
AS-IS business process development
Mapping ERP process
Cloud vendor selection
3. Project development
phase
ERP Prototype outlining
Defining manual process
Designing interface
Project testing
4. Project closure phase Stakeholder signoff
Final documentation
Post project maintenance plan
4.5 Deliverables Out of Scope
The skills and knowledge required to be possessed by the project team members are not
defined in the scope of the project
The future technical specifications are not appropriately designed and demonstrated in this
project scope
4.6 Project Estimated Costs & Duration
Project
Milestone
Date
Estimate Deliverable(s) Included Confidence Level
Milestone 1:
Completion of
project initiation
phase
Thu 7/5/18 Defining project scope
and company
background
Identification of project
team
Stakeholders
identification for the
business blueprint
Identifying system
environment
Technical infrastructure
development
Identification of
production ambiance
Medium
Milestone 2:
Completion of
project planning
Wed 9/5/18 AS-IS business
process development
Mapping ERP
process
Medium
Confidential Page 5 8/29/2024
4.4 Project Deliverables
Milestone Deliverable
1. Project initiation phase
2. Project planning
phase
Defining project scope and company background
Identification of project team
Stakeholders identification for the business blueprint
AS-IS business process development
Mapping ERP process
Cloud vendor selection
3. Project development
phase
ERP Prototype outlining
Defining manual process
Designing interface
Project testing
4. Project closure phase Stakeholder signoff
Final documentation
Post project maintenance plan
4.5 Deliverables Out of Scope
The skills and knowledge required to be possessed by the project team members are not
defined in the scope of the project
The future technical specifications are not appropriately designed and demonstrated in this
project scope
4.6 Project Estimated Costs & Duration
Project
Milestone
Date
Estimate Deliverable(s) Included Confidence Level
Milestone 1:
Completion of
project initiation
phase
Thu 7/5/18 Defining project scope
and company
background
Identification of project
team
Stakeholders
identification for the
business blueprint
Identifying system
environment
Technical infrastructure
development
Identification of
production ambiance
Medium
Milestone 2:
Completion of
project planning
Wed 9/5/18 AS-IS business
process development
Mapping ERP
process
Medium
Confidential Page 5 8/29/2024
Project Charter
phase Cloud vendor
selection
Risk management
plan
Procurement and
contingency
management plan
Identifying END-tc-
END current business
process
Indentifying process
integrator points
Defining end-tc-END
Future business
process for Wiser
Milestone 3:
Completion of
project
development
phase
Thu 12/13/18 ERP Prototype
outlining
Prototype designing
Defining manual
process
Designing interface
Technical
specification
Coding
Cloud platform
identification and
incorporation
High
Milestone 4:
Completion of
project testing
phase
Wed 1/30/19 Unite testing
Integrated testing
Acceptance testing
Medium
Milestone 5:
Completion of
project closure
phase
Thu 2/7/19 Stakeholder signoff
Final documentation
Post project
maintenance plan
Medium
5 PROJECT CONDITIONS
5.1 Project Assumptions
Assumption 1: The project is assumed to be completed within 180 days or 6 months
Assumption 2: The project is assumed to be completed in £80,000
Assumption 3: It is also assumed that with the successful implementation of the cloud based ERP
system Wiser will be able to provide the consumers a much effective and efficient service
Confidential Page 6 8/29/2024
phase Cloud vendor
selection
Risk management
plan
Procurement and
contingency
management plan
Identifying END-tc-
END current business
process
Indentifying process
integrator points
Defining end-tc-END
Future business
process for Wiser
Milestone 3:
Completion of
project
development
phase
Thu 12/13/18 ERP Prototype
outlining
Prototype designing
Defining manual
process
Designing interface
Technical
specification
Coding
Cloud platform
identification and
incorporation
High
Milestone 4:
Completion of
project testing
phase
Wed 1/30/19 Unite testing
Integrated testing
Acceptance testing
Medium
Milestone 5:
Completion of
project closure
phase
Thu 2/7/19 Stakeholder signoff
Final documentation
Post project
maintenance plan
Medium
5 PROJECT CONDITIONS
5.1 Project Assumptions
Assumption 1: The project is assumed to be completed within 180 days or 6 months
Assumption 2: The project is assumed to be completed in £80,000
Assumption 3: It is also assumed that with the successful implementation of the cloud based ERP
system Wiser will be able to provide the consumers a much effective and efficient service
Confidential Page 6 8/29/2024
Project Charter
5.2 Project Issues
Priority Criteria
1−High-priority/critical-path issue; requires immediate follow-up and resolution.
2−Medium-priority issue; requires follow-up before completion of next project milestone.
3−Low-priority issue; to be resolved prior to project completion.
4−Closed issue.
# Date Priority Owner Description Status & Resolution
1 Critical path
issues
High Project
manager
In order to
complete any
project, it is not
necessary that
there will be only
one path rather
there are many
directions to be
followed through
which a project
can be
completed within
estimated
budget and time.
If the project
manager fails to
identify the most
suitable path to
direct the project
towards its
objectives then
the entire project
may become a
failure
After identification of the
critical path issues
necessary actions should
be undertaken for
resolving the issues of
project progress path. The
project is expected to be
complete
2 Issues with
post project
maintenanc
e plan
High System
develope
r
As the project is
about
implementation
of a cloud based
ERP system for
storing
information in a
much secured
way thus if the
project manager
and system
developer fails
to identify all
necessary post
implementation
program then for
further system
level issues
there will be no
availability of
Besides current
maintenance planning the
system developers are
needed to consider all
possible post project
maintenance planning as
well.
Confidential Page 7 8/29/2024
5.2 Project Issues
Priority Criteria
1−High-priority/critical-path issue; requires immediate follow-up and resolution.
2−Medium-priority issue; requires follow-up before completion of next project milestone.
3−Low-priority issue; to be resolved prior to project completion.
4−Closed issue.
# Date Priority Owner Description Status & Resolution
1 Critical path
issues
High Project
manager
In order to
complete any
project, it is not
necessary that
there will be only
one path rather
there are many
directions to be
followed through
which a project
can be
completed within
estimated
budget and time.
If the project
manager fails to
identify the most
suitable path to
direct the project
towards its
objectives then
the entire project
may become a
failure
After identification of the
critical path issues
necessary actions should
be undertaken for
resolving the issues of
project progress path. The
project is expected to be
complete
2 Issues with
post project
maintenanc
e plan
High System
develope
r
As the project is
about
implementation
of a cloud based
ERP system for
storing
information in a
much secured
way thus if the
project manager
and system
developer fails
to identify all
necessary post
implementation
program then for
further system
level issues
there will be no
availability of
Besides current
maintenance planning the
system developers are
needed to consider all
possible post project
maintenance planning as
well.
Confidential Page 7 8/29/2024
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Project Charter
# Date Priority Owner Description Status & Resolution
solution.
5.3 Project Risks
# Risk Area Likelihood Risk Owner Project Impact-Mitigation Plan
1 Lack of
financial
support
High Finance
manager and
project
sponsor
It is the responsibility of the project
sponsors and the finance manager
to develop a feasibility study so that
the necessary capital that might be
needed for the successful
completion of cloud based ERP
system can be estimated. It is
expected that if necessary financial
support and given to the project
developer at the very project
initiation phase then within the
estimated time the system will be
able to deliver the system
considering all specifications in
terms of operational and functional
activities.
2 Improper
resource
allocation
High HR manager In order to successfully complete a
project, based on skills and
knowledge, resources must be
allocated to each task. It is the
responsibility of the allotted human
resources to complete their allotted
job roles. With the help of different
performance measurements matrix
the skills of the resources will be
measured accordingly. Then, based
on the skills the resources are to be
allotted for each work package.
3 Lack of
technical
expertise
Medium Resource
manager
For the successful implementation
of the cloud based ERP system,
wiser should arrange on job training
and development program and
workshop as well. It is expected
that if the project team members
attend those workshop and training
program professionally then
automatically their overall skill will
be increased. If they apply those
skills in the real world then the
overall efficacy of the overall ERP
system will automatically increase.
4 Lack of
security
High System
developer
It is the responsibility of the system
developer and security manager to
take possible actions on ERP
system security in terms of
Confidential Page 8 8/29/2024
# Date Priority Owner Description Status & Resolution
solution.
5.3 Project Risks
# Risk Area Likelihood Risk Owner Project Impact-Mitigation Plan
1 Lack of
financial
support
High Finance
manager and
project
sponsor
It is the responsibility of the project
sponsors and the finance manager
to develop a feasibility study so that
the necessary capital that might be
needed for the successful
completion of cloud based ERP
system can be estimated. It is
expected that if necessary financial
support and given to the project
developer at the very project
initiation phase then within the
estimated time the system will be
able to deliver the system
considering all specifications in
terms of operational and functional
activities.
2 Improper
resource
allocation
High HR manager In order to successfully complete a
project, based on skills and
knowledge, resources must be
allocated to each task. It is the
responsibility of the allotted human
resources to complete their allotted
job roles. With the help of different
performance measurements matrix
the skills of the resources will be
measured accordingly. Then, based
on the skills the resources are to be
allotted for each work package.
3 Lack of
technical
expertise
Medium Resource
manager
For the successful implementation
of the cloud based ERP system,
wiser should arrange on job training
and development program and
workshop as well. It is expected
that if the project team members
attend those workshop and training
program professionally then
automatically their overall skill will
be increased. If they apply those
skills in the real world then the
overall efficacy of the overall ERP
system will automatically increase.
4 Lack of
security
High System
developer
It is the responsibility of the system
developer and security manager to
take possible actions on ERP
system security in terms of
Confidential Page 8 8/29/2024
Project Charter
# Risk Area Likelihood Risk Owner Project Impact-Mitigation Plan
encryption, firewall and strong
password. With the help of
encryption apart from the sender
and the receiver no third party will
be able to access information from
the server. The firewall can keep
the information transmission
channel secured from the external
unauthenticated and unauthorized
users. The security key should not
be shared with any outsiders.
5.4 Project Constraints
For this particular project triple project constraints are considered in terms of project time, scope
and budget. After analyzing the service details offered by Wiser it is determined that, for the
successful implementation of the cloud based ERP system the total cost estimated in £80,000.
Besides cost the total time that has been estimated is around 6 months or 180 days. The scope
of the project is to design and implement a cloud based ERP system for building employer brands
that can attract people and guide them throughout their dream career. The timeline, cost and the
resources details allotted for each phase are also elaborated in the following section:
Task Name Duration Start Finish Predecessor
s Resource Names
Cloud based ERP system
development in Wiser 180 days Fri 6/1/18 Thu 2/7/19
Project initiation phase 25 days Fri 6/1/18 Thu 7/5/18
Defining project scope
and company background 3 days Fri 6/1/18 Tue 6/5/18 project manager
Identification of project
team 5 days Wed 6/6/18 Tue 6/12/18 2 project manager,
project sponsor
Stakeholders
identification for the
business blueprint
6 days Wed 6/13/18 Wed 6/20/18 3 Human resource
manager
Identifying system
environment 3 days Wed 6/13/18 Fri 6/15/18 3 business analyst
Technical infrastructure
development 5 days Thu 6/21/18 Wed 6/27/18 4 system developer
Identification of
production ambiance 6 days Thu 6/28/18 Thu 7/5/18 5,6 business analyst
Milestone 1:
Completion of project
initiation phase
0 days Thu 7/5/18 Thu 7/5/18 7
Project planning phase 44 days Fri 7/6/18 Wed 9/5/18
AS-IS business
process development 5 days Fri 7/6/18 Thu 7/12/18 8 system developer
Mapping ERP process 6 days Fri 7/13/18 Fri 7/20/18 10
Application
programming
manager
Cloud vendor selection 4 days Mon 7/23/18 Thu 7/26/18 11 project sponsor
Risk management plan 6 days Fri 7/27/18 Fri 8/3/18 12 project manager
Procurement and 9 days Mon 8/6/18 Thu 8/16/18 12,13 business analyst
Confidential Page 9 8/29/2024
# Risk Area Likelihood Risk Owner Project Impact-Mitigation Plan
encryption, firewall and strong
password. With the help of
encryption apart from the sender
and the receiver no third party will
be able to access information from
the server. The firewall can keep
the information transmission
channel secured from the external
unauthenticated and unauthorized
users. The security key should not
be shared with any outsiders.
5.4 Project Constraints
For this particular project triple project constraints are considered in terms of project time, scope
and budget. After analyzing the service details offered by Wiser it is determined that, for the
successful implementation of the cloud based ERP system the total cost estimated in £80,000.
Besides cost the total time that has been estimated is around 6 months or 180 days. The scope
of the project is to design and implement a cloud based ERP system for building employer brands
that can attract people and guide them throughout their dream career. The timeline, cost and the
resources details allotted for each phase are also elaborated in the following section:
Task Name Duration Start Finish Predecessor
s Resource Names
Cloud based ERP system
development in Wiser 180 days Fri 6/1/18 Thu 2/7/19
Project initiation phase 25 days Fri 6/1/18 Thu 7/5/18
Defining project scope
and company background 3 days Fri 6/1/18 Tue 6/5/18 project manager
Identification of project
team 5 days Wed 6/6/18 Tue 6/12/18 2 project manager,
project sponsor
Stakeholders
identification for the
business blueprint
6 days Wed 6/13/18 Wed 6/20/18 3 Human resource
manager
Identifying system
environment 3 days Wed 6/13/18 Fri 6/15/18 3 business analyst
Technical infrastructure
development 5 days Thu 6/21/18 Wed 6/27/18 4 system developer
Identification of
production ambiance 6 days Thu 6/28/18 Thu 7/5/18 5,6 business analyst
Milestone 1:
Completion of project
initiation phase
0 days Thu 7/5/18 Thu 7/5/18 7
Project planning phase 44 days Fri 7/6/18 Wed 9/5/18
AS-IS business
process development 5 days Fri 7/6/18 Thu 7/12/18 8 system developer
Mapping ERP process 6 days Fri 7/13/18 Fri 7/20/18 10
Application
programming
manager
Cloud vendor selection 4 days Mon 7/23/18 Thu 7/26/18 11 project sponsor
Risk management plan 6 days Fri 7/27/18 Fri 8/3/18 12 project manager
Procurement and 9 days Mon 8/6/18 Thu 8/16/18 12,13 business analyst
Confidential Page 9 8/29/2024
Project Charter
contingency management
plan
Identifying END-tc-
END current business
process
6 days Fri 8/17/18 Fri 8/24/18 14 system developer
Indentifying process
integrator points 3 days Mon 8/27/18 Wed 8/29/18 15 project manager
Defining end-tc-END
Future business process
for Wiser
5 days Thu 8/30/18 Wed 9/5/18 16 business analyst
Milestone 2:
Completion of project
planning phase
0 days Wed 9/5/18 Wed 9/5/18 17
Project development
phase 71 days Thu 9/6/18 Thu 12/13/18
ERP Prototype
outlining 9 days Thu 9/6/18 Tue 9/18/18 18 system developer
Prototype designing 10 days Wed 9/19/18 Tue 10/2/18 20
Application
programming
manager
Defining manual
process 12 days Wed 10/3/18 Thu 10/18/18 21 system developer
Designing interface 12 days Wed 10/3/18 Thu 10/18/18 21
Application
programming
manager
Technical specification 10 days Fri 10/19/18 Thu 11/1/18 22,23
Application
programming
manager ,project
manager
Coding 10 days Fri 11/2/18 Thu 11/15/18 24
Application
programming
manager
Cloud platform
identification and
incorporation
20 days Fri 11/16/18 Thu 12/13/18 25 project manager
Milestone 3:
Completion of project
development phase
0 days Thu 12/13/18 Thu 12/13/18 26
Project testing phase 34 days Fri 12/14/18 Wed 1/30/19
Unit testing 10 days Fri 12/14/18 Thu 12/27/18 27 system tester
Integrated testing 12 days Fri 12/28/18 Mon 1/14/19 29 system tester
Acceptance testing 12 days Tue 1/15/19 Wed 1/30/19 30 system tester
Milestone 4:
Completion of project
testing phase
0 days Wed 1/30/19 Wed 1/30/19 31
Project closure phase 6 days Thu 1/31/19 Thu 2/7/19
Stakeholder signoff 2 days Thu 1/31/19 Fri 2/1/19 32 finance manager
Final documentation 2 days Mon 2/4/19 Tue 2/5/19 34 project sponsor
Post project
maintenance plan 2 days Wed 2/6/19 Thu 2/7/19 35 project manager
Milestone 5:
Completion of project
closure phase
0 days Thu 2/7/19 Thu 2/7/19 36
Confidential Page 10 8/29/2024
contingency management
plan
Identifying END-tc-
END current business
process
6 days Fri 8/17/18 Fri 8/24/18 14 system developer
Indentifying process
integrator points 3 days Mon 8/27/18 Wed 8/29/18 15 project manager
Defining end-tc-END
Future business process
for Wiser
5 days Thu 8/30/18 Wed 9/5/18 16 business analyst
Milestone 2:
Completion of project
planning phase
0 days Wed 9/5/18 Wed 9/5/18 17
Project development
phase 71 days Thu 9/6/18 Thu 12/13/18
ERP Prototype
outlining 9 days Thu 9/6/18 Tue 9/18/18 18 system developer
Prototype designing 10 days Wed 9/19/18 Tue 10/2/18 20
Application
programming
manager
Defining manual
process 12 days Wed 10/3/18 Thu 10/18/18 21 system developer
Designing interface 12 days Wed 10/3/18 Thu 10/18/18 21
Application
programming
manager
Technical specification 10 days Fri 10/19/18 Thu 11/1/18 22,23
Application
programming
manager ,project
manager
Coding 10 days Fri 11/2/18 Thu 11/15/18 24
Application
programming
manager
Cloud platform
identification and
incorporation
20 days Fri 11/16/18 Thu 12/13/18 25 project manager
Milestone 3:
Completion of project
development phase
0 days Thu 12/13/18 Thu 12/13/18 26
Project testing phase 34 days Fri 12/14/18 Wed 1/30/19
Unit testing 10 days Fri 12/14/18 Thu 12/27/18 27 system tester
Integrated testing 12 days Fri 12/28/18 Mon 1/14/19 29 system tester
Acceptance testing 12 days Tue 1/15/19 Wed 1/30/19 30 system tester
Milestone 4:
Completion of project
testing phase
0 days Wed 1/30/19 Wed 1/30/19 31
Project closure phase 6 days Thu 1/31/19 Thu 2/7/19
Stakeholder signoff 2 days Thu 1/31/19 Fri 2/1/19 32 finance manager
Final documentation 2 days Mon 2/4/19 Tue 2/5/19 34 project sponsor
Post project
maintenance plan 2 days Wed 2/6/19 Thu 2/7/19 35 project manager
Milestone 5:
Completion of project
closure phase
0 days Thu 2/7/19 Thu 2/7/19 36
Confidential Page 10 8/29/2024
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Project Charter
6 Project Structure Approach
[Replace this text with a description of how the project will be structured and what
approach will be used to manage the project.
The project constraints are dependent on each other. In order to measure the project
level dependencies the project and the company both are considered in terms of out
scope ad in scope. Sequential project activities will help the project managers to
complete the cloud based ERP implementation project successful within the estimated
time and budget. Necessary health and safety measures are also to be considered for
the ERP system.
In order to successfully complete the project the project manager has divided the entire
project in small five phases. All of these phases are interrelated to each other and the
input of one phase act as the output to the very next phase. According to the project
plan the five project development phases are project initiation phase, planning phase,
development phase, testing phase an closure phase. For each of the milestones the
project manager, project sponsor and the system developers are responsible
respectively.
7 Project Team Organization Plans
Project Team Role Project Team Member(s) Responsibilities
Project manager John smith Responsible to control and
monitor the cloud based
ERP project
Finance manager Williams Anderson To design feasibility study
and develop a budget pan
for the project
Project sponsor Steven lee To sponsor necessary
capital to support the project
for its successful completion
System developer John carter To develop the cloud based
ERP system
System analysts Thomas mullar To analyze the system that
has been developed
System tester James Anderson To test the system
HR manager To develop the project team
and allot the resources
based on their job roles
Business analysts John Cena To design the system
considering all business
aspects.
Confidential Page 11 8/29/2024
6 Project Structure Approach
[Replace this text with a description of how the project will be structured and what
approach will be used to manage the project.
The project constraints are dependent on each other. In order to measure the project
level dependencies the project and the company both are considered in terms of out
scope ad in scope. Sequential project activities will help the project managers to
complete the cloud based ERP implementation project successful within the estimated
time and budget. Necessary health and safety measures are also to be considered for
the ERP system.
In order to successfully complete the project the project manager has divided the entire
project in small five phases. All of these phases are interrelated to each other and the
input of one phase act as the output to the very next phase. According to the project
plan the five project development phases are project initiation phase, planning phase,
development phase, testing phase an closure phase. For each of the milestones the
project manager, project sponsor and the system developers are responsible
respectively.
7 Project Team Organization Plans
Project Team Role Project Team Member(s) Responsibilities
Project manager John smith Responsible to control and
monitor the cloud based
ERP project
Finance manager Williams Anderson To design feasibility study
and develop a budget pan
for the project
Project sponsor Steven lee To sponsor necessary
capital to support the project
for its successful completion
System developer John carter To develop the cloud based
ERP system
System analysts Thomas mullar To analyze the system that
has been developed
System tester James Anderson To test the system
HR manager To develop the project team
and allot the resources
based on their job roles
Business analysts John Cena To design the system
considering all business
aspects.
Confidential Page 11 8/29/2024
Project Charter
8 PROJECT REFERENCES
Milestone Deliverable
Project initiation document Successful completion of project initiation
Project planning document Successful completion of project planning
Project development
document
Successful completion of project development
Project testing document Successful completion of project testing
Project closure document Successful completion of project closure
9 APPROVALS
Prepared by _ Williams Anderson _________________________________
Project Manager
Approved by ___ Steven lee _______________________________
Project Sponsor
_____<Please fill>_____________________________
Executive Sponsor
________<Please fill>__________________________
Client Sponsor
Confidential Page 12 8/29/2024
8 PROJECT REFERENCES
Milestone Deliverable
Project initiation document Successful completion of project initiation
Project planning document Successful completion of project planning
Project development
document
Successful completion of project development
Project testing document Successful completion of project testing
Project closure document Successful completion of project closure
9 APPROVALS
Prepared by _ Williams Anderson _________________________________
Project Manager
Approved by ___ Steven lee _______________________________
Project Sponsor
_____<Please fill>_____________________________
Executive Sponsor
________<Please fill>__________________________
Client Sponsor
Confidential Page 12 8/29/2024
Project Charter
10 References
Awang, Z., Hashim, N. N., Yaziz, N. M., & Asmuni, N. S. (2015). Assessing customer intention
towards the use of website on online air ticket booking. Editors, 686.
Bowers, J., & Khorakian, A. (2014). Integrating risk management in the innovation
project. European Journal of innovation management, 17(1), 25-40.
Calvo-Mora, A., Navarro-García, A., & Periañez-Cristobal, R. (2015). Project to improve
knowledge management and key business results through the EFQM excellence
model. International Journal of Project Management, 33(8), 1638-1651.
Fernandez-Cavia, J., Rovira, C., Díaz-Luque, P., & Cavaller, V. (2014). Web Quality Index (WQI)
for official tourist destination websites. Proposal for an assessment system. Tourism
management perspectives, 9, 5-13.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Ghosal, S., Chaturvedi, S., Taywade, A., & Jaisankar, N. (2015). Android application for ticket
booking and ticket checking in suburban railways. Indian Journal of Science and
Technology, 8(S2), 171-178.
Larson, E. W., & Gray, C. F. (2014). Project Management: The Managerial Process with MS
Project.
Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education
India.
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking project
management performance and project success. International journal of project
management, 32(2), 202-217.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Taylor & Francis.
Peppard, J., & Ward, J. (2016). The strategic management of information systems: Building a
digital strategy. John Wiley & Sons.
Pinto, J. K., Dawood, S., & Pinto, M. B. (2014). Project management and burnout: Implications of
the Demand–Control–Support model on project-based work. International Journal of
Project Management, 32(4), 578-589.
Ramazani, J., & Jergeas, G. (2015). Project managers and the journey from good to great: The
benefits of investment in project management training and education. International
Journal of Project Management, 33(1), 41-52.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Snyder, C. S. (2014). A Guide to the Project Management Body of Knowledge: PMBOK (®)
Guide. Project Management Institute.
Tamizharsi, T., Suhasaria, P., Agarwal, A., Manchanda, H., & Jain, H. (2017). A Comprehensive
Review of the Bookmyshow Website and System. Imperial Journal of Interdisciplinary
Research, 3(8).
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Young, T.L., 2016. Successful project management. Kogan Page Publishers.
Zwikael, O. (2016). International journal of project management special issue on “project benefit
management”.
Confidential Page 13 8/29/2024
10 References
Awang, Z., Hashim, N. N., Yaziz, N. M., & Asmuni, N. S. (2015). Assessing customer intention
towards the use of website on online air ticket booking. Editors, 686.
Bowers, J., & Khorakian, A. (2014). Integrating risk management in the innovation
project. European Journal of innovation management, 17(1), 25-40.
Calvo-Mora, A., Navarro-García, A., & Periañez-Cristobal, R. (2015). Project to improve
knowledge management and key business results through the EFQM excellence
model. International Journal of Project Management, 33(8), 1638-1651.
Fernandez-Cavia, J., Rovira, C., Díaz-Luque, P., & Cavaller, V. (2014). Web Quality Index (WQI)
for official tourist destination websites. Proposal for an assessment system. Tourism
management perspectives, 9, 5-13.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Ghosal, S., Chaturvedi, S., Taywade, A., & Jaisankar, N. (2015). Android application for ticket
booking and ticket checking in suburban railways. Indian Journal of Science and
Technology, 8(S2), 171-178.
Larson, E. W., & Gray, C. F. (2014). Project Management: The Managerial Process with MS
Project.
Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education
India.
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: linking project
management performance and project success. International journal of project
management, 32(2), 202-217.
Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and
technology. Taylor & Francis.
Peppard, J., & Ward, J. (2016). The strategic management of information systems: Building a
digital strategy. John Wiley & Sons.
Pinto, J. K., Dawood, S., & Pinto, M. B. (2014). Project management and burnout: Implications of
the Demand–Control–Support model on project-based work. International Journal of
Project Management, 32(4), 578-589.
Ramazani, J., & Jergeas, G. (2015). Project managers and the journey from good to great: The
benefits of investment in project management training and education. International
Journal of Project Management, 33(1), 41-52.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Snyder, C. S. (2014). A Guide to the Project Management Body of Knowledge: PMBOK (®)
Guide. Project Management Institute.
Tamizharsi, T., Suhasaria, P., Agarwal, A., Manchanda, H., & Jain, H. (2017). A Comprehensive
Review of the Bookmyshow Website and System. Imperial Journal of Interdisciplinary
Research, 3(8).
Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.
Young, T.L., 2016. Successful project management. Kogan Page Publishers.
Zwikael, O. (2016). International journal of project management special issue on “project benefit
management”.
Confidential Page 13 8/29/2024
1 out of 13
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.