Solved by verified expert:I have attached my project and till now whatever i have done. It’s writing about upgrading legacy system using project management methodology. I have attached question and my project and also book for review. You will need to read my project and question to work on the parts that are left. I need two parts for now and they are : 1)Quality Management2) Communications Management
information_technology_project_schwalbe.zip
my_project.docx
project_manageent_plan.docx
Unformatted Attachment Preview
Purpose of Project Management Plan
The project management plan will serve as a central repository for all project planning documents that
are used to ensure successful execution and delivery of the project [1]. This document will provide a
natural sequence of tasks that must be undertaken to complete the project within the constraints of
time, scope, and budget. The document will also guide and inform project team members about the
overarching priorities of the project, and facilitate a common understanding about the project’s goals
and intended outcomes amongst stakeholders. The plan will be updated and maintained throughout the
project’s lifecycle to guarantee accuracy. Finally, the plan will serve as a template to be referenced for
future projects to emphasize lessons learned, and reduce the likelihood of repeating mistakes.
Project Name: “Less is More; 2017 Legacy System Consolidation Project”
Project Overview: SSK, Inc.’s is currently working with several legacy systems to fulfill daily business
operations. These systems are independent of one another and lack any middleware to interface with
one another. This partition between system is resulting in silos within the business units causing
coordination of tasks to become increasingly difficult and frustrating for users. Additionally, as the
systems continue to age, less support is available to maintain the software which is causing the system
to become less efficient and decline in performance. The existence of several systems is also a financial
burden on the company as SSK must maintain an increasing number of vendor licenses often with
overlapping user requiring access to more than system. The aim of this project is to consolidate legacy
systems into an all-in-one platform where users can achieve all of their business tasks in one place.
Creating interfaces between the systems will allow users to perceive the system as one application and
will further streamline daily activities. Ultimately, users will have a more positive interaction with the
system, leading to higher morale, increased productivity, and long-run cost savings.
Project Sponsor: CEO.
Project Managers: …………………………………………………
Project Assumptions & Constraints
Assumptions:
•
Software re-use and use of Commercial-Off-The-Shelf software (COTS) will be
emphasized
•
Prototyping will be encouraged to help define and refine functional requirements
•
Performance expectations: System will be continuously monitored for any performance
issues
•
Financial: Sufficient funds are available to migrate the systems and process
improvements
•
Technology people have enough knowledge, skills and abilities to support systems
migration to more complex integrated systems
•
The finally integrated and improved system will go through multiple stages of testing to
ensure it performs as per user’s expectations
•
Right stakeholders are identified who meet regularly to promote information sharing,
knowledge transfer and collaboration
•
A risk mitigation plan will be prepared if the new system fails.
•
New system will be agile enough to accommodate any future technological changes.
•
Existing legacy systems’ logic is to used effectively as those logics are business tested
and certified.
•
System migration will follow modular approach where legacy systems will be migrated
in parts instead of the whole systems.
•
Proper metrics are to be maintained to track system migration for decision making and
comparison with legacy systems.
Constraints:
•
Technology people skill level may not be as per the expectations of the final system.
They may not be familiar with the new technology.
•
System user may resist using new systems. Adequate trainings need to be provided to
increase new system acceptance.
•
End user training on new system may be performed multiple times until user gets familiar
with it.
•
Few systems may not support new technology and may break during migration process.
•
Project may take more time then anticipated
•
Project cost may exceed budget as integration and process improvement may require
more skilled resources and advanced technologies.
•
Project may involve/require other advanced technologies for successful system migration.
•
System migration requires availability of technical people who have deep understanding
of the existing legacy system so that plan to migrate can be developed based on details
provided by them.
Work Breakdown Structure(WBS)
Business systems modernization WBS
Legacy
Applications
Modernization
Project
Business Process
Identify
processes
Conduct
business
process training
Document
processes
Software
Develop RFP
Review systems
Hardware
Upgrade
hardware
Setup Project
Office
System
Implementation
Documentation
Training
Support
Setup
Procedures
Upgrade
Helpdesk
Provide Support
Select legacy
system
Operation and
Maintenance
Configuration
Sign contract
Development
Receive
software
Data Migration
Renew support
Testing
Review
processes
Deployment Plan
The deployment plan is very important in detailing how the system will be deployed, installed and
how the transition from implementation to development will be carried out. The various resources
that are needed for deployment process will be defined in this plan.
The deployment plan has been developed to cover the consolidation of legacy systems into one
platform which will allow users to achieve various business operational needs that they have.
Key Assumptions
1. The deployment will be after successful procurement of all the necessary hardware and
software requirements for the system
2. The vendor of the system will provide the installation technical staff together with the
training staff for the project
Description of Deployment
After the off-the-shelf system has been purchased, it will first in a stand-alone environment to
ensure that the various functionalities meet the needs of the company and to ensure that these
functionalities are functioning correctly.
A system pilot will then be carried out where users will try using the system so that they can gain
the basic skills about how to use the system and to make any recommendations for changes that
should be made. This process will be guided by trainers and support staff who will have a better
understanding of how the system works and who can explain the technical aspects of the system.
After all the necessary changes have been made, the system will be integrated with the current
legacy system to allow for interoperability and data transfer between the two system with an aim
of ensuring a smooth transition.
To ensure that there is a smooth transition of the implementation process, the system will be
deployed in phases. These phases will be based on the different organizational functions.
Points of Contact
To effectively ensure the deployment of the project, the following resources will be used:
Role
Name
Project Sponsor
Project Manager
Deployment Tasks
There are various tasks that will be carried out to deploy the project in an incremental way. These
tasks will include:
•
Scheduling of the deployment phases
•
Training of users and personnel
•
Preparation of user manuals and issuance them to users
•
Technical assistance setup
•
Procurement of the software application
•
Procurement of the hardware application
•
Hosting the system
•
Installation of application
•
Accounts administrative functionalities.
Deployment Schedule
The deployment process will be carried out in 15 days with the tasks being carried out as shown
in the Gantt chart below:
Hardware and Software Requirements
To ensure that the system is successfully deployed various hardware and software applications will
be required:
1. Desktop computers and laptops for end users
2. Projector for presentations
3. Smartphones and tablets for demos
4. Demo system to train users
5. Internet connectivity and networking infrastructure for data migration and system access
6. Application to be implemented
7. Legacy system
8. Physical facilities- workspace for testing and assembling the hardware and test
components, boardroom for user training
9. Hosting service provider
Transition to Live Operations
To ensure a successful transition, the first part will include ensuring that user accounts are
created for all users and unique passwords issued to them.
All hardware devices will be issued to the expected system users of the company together with
the set up for new operations required to run the system effectively.
All stakeholders will be notified of the deployment with an email notification sent to all the
clients, users and employees through email.
Operations and Maintenance
The system will be hosted on the cloud to allow users access it from any location as long as
they have an internet connection. The vendor to be used to host the system was identified
during the development process and all the tests with the host were carried out during
development.
Given that the system is an over the counter system, an SLA with the vendor will be created to
ensure that they have the necessary support and maintenance structures in place. This will
ensure over 90% system availability and ensure that any bugs are rectified within the shortest
time possible.
Change Control Management
The purpose of the change control management is to ensure that a procedure in which changes are
proposed, accepted, monitored and controlled is devised. The control procedures that are identified
helps in governing changes to the project scope that is not limited to change in the work breakdown
structure and the requirements, from project inception to project completion. This will also control
changes to the project schedule and the cost of the project.
Procedures for Change Identification
Any of the project members or stakeholders can make a change request to the project manager
based on the need that they identify for a change of the project. After the identification of the
change, a Change Request form will be filled where various specified details are filled. The change
requester fills the first part of the change request form and then the project manager records the
change in a Change Control Log that tracks the implementation of the change request throughout
the project. The filled change request then goes through a change authorization process where the
change committee considers the change and then it is approved for implementation or it is rejected.
Change Analysis Process
After the change request has been filled in the second section, the project manager will fill the
second part of the change request form. In this part, details such as the amount and the type of
work that needs to be carried out to actualize the change will be filled. The impact that the change
has on the various project constraints will then be analyzed to determine whether it is feasible to
carry out the change process.
After an analysis of the impact that the change will have on the different project constraints, the
project manager will then make a decision whether the project sponsor should consider this change
request.
Change Approval
The change request form is then forwarded to the change committee, who together with the project
sponsor makes the final decision to ensure that the change is implemented. This is done by
reviewing the change request and filing the final part of the change request form and then returning
the same to the project manager.
If the change committee approves the change request, the project manager will update all the
necessary documentations to ensure that the project scope reflects the changes that have been made
to the project. The project manager to ensure that resources, budget, and schedule reflects the
requested change then creates an updated implementation plan.
If the change request is rejected then the change request log will reflect the same.
Change Tracking
The change control log will be a master log of all the change requests that have made for a project
with the details of who has made the change request. After a change request has been approved,
the project manager fills the fourth part of the change request form and the same update will be
made on the change request log.
Milestones:
The primary goal of the project is to migrate legacy systems to modern technologies. To achieve this
goal, organization has set several milestones as the project development progresses. We have identified
following lists of milestones to be achieved as the project progress to measure project progress:
Milestone
Description
Date
Project proposal design
Feasibility analysis, proposed system basic concepts
and new technology to be used are identified along
with the process improvement strategies
10/01/2017
Project proposal review
Review of identified feasibility analysis, proposed
technologies and process improvement is performed
10/03/2017
Initiate Requirement
gathering
Requirement gathering on the basis of functionalities 10/03/2017
of the existing Legacy systems is initiated.
Complete Requirements
Gathering
Requirement gathering is completed.
10/10/2017
Requirement approval
Baselined requirements are approved by
stakeholders.
10/12/2017
Preliminary design
Architectural design of the proposed system is
developed.
10/20/2017
Preliminary design review
Proposed architectural design is reviewed.
10/23/2017
Critical design review
Detailed design to implement proposed architectural
designs are reviewed
10/25/2017
Complete Design
Detailed design is completed and reviewed
11/10/2017
Test Plan design
All requirements for new system must be
determined to base design on for test planning
11/24/2017
Test Plan review
Developed test plan is reviewed and approved by
stakeholders
12/01/2017
Complete Coding
Migration of old system is completed using new
technologies and proposed process improvements
12/29/2017
Test readiness review
Developed system is verified against baseline
requirements
01/05/2018
System test review
System is verified to be ready for functional
validation
01/12/2018
Complete Testing and
Debugging
Coding is verified and identified issues are fixed
01/26/2018
Operational readiness
review
System is certified to be used in production
environment
01/31/2018
Complete Transition of
modern system to
Production
Completed software and documentation
transitioned to operations group to begin production
01/31/2018
Note: Milestones are estimated dates based on PMP deliverables dates.
Dependencies:
✓ Project may have limited number of experts on old technologies of the legacy system. It
may get challenging to understand detailed design and working of the existing legacy
systems.
✓ Project may have limited skilled professionals on latest technology to be implemented
to develop the new system and project may not take benefit of concurrent tasks
completion due to limited number of resources.
✓ Project development can not start until system design and requirements are base lined.
✓ Project will mostly rely on Finish-to-start dependency where other tasks can only be
started once previous tasks is completed to follow modular development approach for
the successful migration of the system.
✓ Since most of the system will be developed using COTS products. Upgrade and
enhancement of the system will highly rely on the support from the COTS product’s
owner company.
✓ Users satisfaction on the new system is dependent on the quality of training material
prepared and quality of the training given.
✓ The new system proposed changes are dependent and must satisfy current federal
government rules defined
Earned Value Management System
BUSINESS PROCESS ACTIVITIES
Activity
Planned Value
1.1 Identify
Processes
1.2 Conduct
Business
Process
Training
1.3 Document
1.4 Review
Processes
SOFTWARE ACTIVITIES
$2,000
Rate of
Performance
100%
Earned
Value
$2,000
Actual
Cost
$2,000
Cost
Variance
$0
Schedule
Variance
0
$7,000
90%
$6,300
$7,700
$-1,400
-700
$2,200
$4,500
100%
100%
$2,200
$4,500
$2,200
$4,500
$0
$0
0
0
Activity
2.1 Develop
RFP
2.2 Review
Systems
2.3 Select
Legacy
2.4 Renew
Support
Planned
Value
$3,000
Rate of
Performance
100%
Earned
Value
$3,000
Actual
Cost
$3,000
Cost
Variance
$0
Schedule
Variance
0
$10,000
75%
$7,500
$12,500
$-5,000
-2,500
$1,000
95%
$950
$1,050
$-100
-50
$20,000
100%
$20,000
$20,000
$0
0
HARDWARE ACTIVITIES
Activity
3.1 Upgrade
Hardware
3.2 Setup
Project Office
3.3 Operation
& Maintenance
Planned
Value
$75,000
Rate of
Performance
100%
Earned
Value
$75,000
Actual
Cost
$75,000
Cost
Variance
$0
Schedule
Variance
0
$50,000
83%
$41,500
$58,500
$-17,000
-8,500
$150,000
95%
$142,500
$157,500
$-15,000
-7,500
SYSTEM IMPLEMENTATION ACTIVITIES
Activity
4.1
Documentation
4.2 Training
4.3 Configuration
4.4 Development
4.5 Data
Migration
4.6 Testing
Planned
Value
$35,000
Rate of
Performance
100%
Earned
Value
$35,000
Actual
Cost
$35,000
Cost
Variance
$0
Schedule
Variance
0
$50,000
$85,000
$500,000
$120,000
100%
100%
90%
80%
$50,000
$85,000
$450,000
$96,000
$50,000
$85,000
$550,000
$130,000
$0
$0
$-100,000
$-34,000
0
0
-50,000
-24,000
$500,000
87%
$435,000
$505,000
$-70,000
-5,000
SUPPORT ACTIVITIES
Activity
5.1 Setup
Procedures
5.2 Upgrade
Helpdesk
5.3 Provide
Support
Planned
Value
$10,000
Rate of
Performance
100%
Earned
Value
$10,000
Actual
Cost
$10,000
Cost
Variance
$0
Schedule
Variance
0
$35,000
100%
$35,000
$35,000
$0
0
$300,000
100%
$300,000
$300,000
$0
0
TOTAL
Planned Value
Average Rate
Earned Value
Actual Cost
Cost Variance Schedule
of
Variance
Performance
$1,959,700
95%
$1,801,450
$2,043,950
($242,500)
(98,250)
Project Team training
Training will be conducted with SSK, Inc.’s staff on new tools and technologies. Purpose of the training is
to outline the SSK, Inc.’s initiative to migrate existing legacy systems to all-in-one platform. Training will
be focused on new project requirements, technology used, process improvements and strategies
developed to implement the new systems. All employees will be trained on new systems to make them
familiar with the new technologies and platforms. This training will enable employees to work more
efficiently and will result in organizational performance improvement.
Points of Contact
To provide training on the improved systems, following lists of contacts is identified. These points of
contact will handle entire training process, will drive multiple training sessions to ensure each user is
comfortable using the new tools.
Role
Training Content Developer
Name
Meder Vladimir
Training Supervisor
Rachael Hammerstein
Lead Training coordinator
Joran Piccard
Asst. Training coordinator
Jane Choulai
Training Scheduler
Teresa Hemesly
Facilities Coordinator
Valentine Wachberger
Contact Number
408-629-0589
209-686-3953
413-793-7432
823-353-5305
683-938-8273
849-210-3503
Purpose of training plan
XYZ corporation has decided to migrate their legacy systems to new technologies to improve overall
organizational performance and to achieve high customer satisfaction. To achieve this goal, training staff
has developed training schedule and training materials on new systems to address the organizational needs.
The XYZ corporation has contracted certified training providers on new technologies. Also, internal
training staff will provide training on how to use new enhanced systems efficiently. To achieve this goal,
strategy will be to train technical support team on new technologies and all employees on new system.
Training Schedule:
Each group of employees from XYZ corporation will be provided with three days of training on the new
system. Following is the planned training schedule:
Day 1:
Time
8:00
8:30
8:30
10:00
10:00
10:15
10:15
11:45
Subject
Location
– Introductions to new system T …
Purchase answer to see full
attachment
You will get a plagiarism-free paper and you can get an originality report upon request.
All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades
Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.
You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.
Read moreEach paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.
Read moreThanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.
Read moreYour email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.
Read moreBy sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.
Read more