Project Management Assignment: XP to Windows 2016 Upgrade Project

This project management assignment details the upgrade of a single-operator business from XP to Windows 2016. The project aims to resolve security issues and align with IT security guidelines by upgrading the operating system. The scope includes upgrading from XP to Windows 2016, determining project scope, securing data, and installing necessary hardware. The project's high-level requirements involve requirement analysis, budget development, and obtaining approvals. Deliverables include resource definition, software specifications, and a test plan. The project timeline spans 17.88 days with a budget of $86,590, encompassing resource costs, material expenses, and other costs. The implementation plan outlines software development, testing, training, and deployment phases. The assignment also includes a detailed budget breakdown and a Gantt chart illustrating the project schedule.

Running head: PROJECT MANAGEMENT
Topic-A single-operator business is upgrading from XP to Windows 2016.
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
Overview..........................................................................................................................................2
1. Project background and description.............................................................................................2
2. Project scope................................................................................................................................3
3. High level requirements...............................................................................................................3
4. Deliverables and Milestones........................................................................................................4
5. Affected parties............................................................................................................................5
6. Affected business processes or Systems......................................................................................5
7. Specific Exclusion from scope....................................................................................................6
8. Implementation Plan....................................................................................................................6
9. High-level budget and timeline/ schedule...................................................................................7
9.1 Budget of the project.............................................................................................................7
9.2 Schedule of the project..........................................................................................................8
Bibliography..................................................................................................................................14

2
PROJECT MANAGEMENT
Overview
The project mainly reflects a single-operator business who wants upgrade its information
technology software from XP to Windows 2016. It is identified that the single operator business
operating system is not supported by the Microsoft and as a result the business faces number of
problem. In order to resolve the challenges the organization wants to upgrade its operating
system. The up gradation will be completed in 17.88 days and within the budget that is around
$86,560. The budget as well as time of the project must be estimated properly in order to avoid
risk.
1. Project background and description
The paper focuses on the project of information technology software upgrade. It is
identified that the operating system that the organization is currently using is not supported by
Microsoft and as a result the organization is facing number of issues as well as challenges. It is
analyzed that the most important issues that the company is facing is security related issue. The
confidential data as well as information of the organization can be misused by others due to
absence of proper security. In order to resolve the challenges as well as issue, the organization
wants to upgrade its XP to Windows 2016.
It is identified that implementation of a corporate PC standard on all the PC of the
organization can only be done by deploying proper standard of desktop image that is mainly
based on Windows 16. The project will align with the image of the organization by following
proper IT security guidelines. It is quite important to move all data to the network drives. The
project also aims to upgrade or replace the PC’s that are not working properly.

3
PROJECT MANAGEMENT
2. Project scope
The project scope is mainly categorized into in scope and out scope.
The in-scope of the project is as follows:
 Up gradation from XP to Windows 2016
 Determining the project scope
 Determining resources as well as proper time for completing the project
 Securing the information as well as data
 Installing hardware that don’t meet the requirement of up gradation
The out scopes of the project are as follows:
 The information about the supplier is not present
 The time of the project is not increased for managing scope creep
3. High level requirements
The high-level project requirements are as follows:
 Conducting the requirement analysis
 Drafting the different specification of the software
 Developing proper budget for the project
 Reviewing the specification of software
 Ability of proper interfacing with different system of warehouse
 Incorporating software specification
 Developing proper delivery timeline

4
PROJECT MANAGEMENT
 Ability of incorporating proper routing
 Obtaining proper approval for proceeding
 Securing different needed resources.
 Analyzing hardware requirement of the project
4. Deliverables and Milestones
The deliverable of the project is as follows:
 Developing as well defining various resources of the project
 Drafting all the specifications of the software
 Developing appropriate functional specifications
 Developing appropriate prototype as per various functional specifications
 Developing proper test plan for the project
 Developing proper training support
 Development of proper deployment methodology or strategy
The milestone of the project is provided in the table below:
Task Name Start
Milestone 1: Completion of scope Mon 11/27/17
Milestone 2: Completion of analysis Tue 11/28/17
Milestone 3: Designing completion Fri 12/1/17
Milestone 4: Development completion Mon 12/4/17
Milestone 5:Integration testing completion Fri 12/8/17
Milestone 6:Completion of training materials Tue 12/12/17

5
PROJECT MANAGEMENT
Milestone 7:Completion of documentation Thu 12/14/17
Milestone 8:Pilot completion Fri 12/15/17
Milestone 9: Completion of deployment Tue 12/19/17
Milestone 10: Completion of post implementation review Tue 12/19/17
5. Affected parties
The affected parties of the project are provided in the table below:
Title Influence
Chief executive officer High
Engineering leader Medium
Vice president Low
Project manager High
Chief Financial officer High
Project management director Medium
6. Affected business processes or Systems
The affected business procedures or systems are as follows:
Payroll system of the company: It is identified that due to up gradation from XP to
windows 16, the organization requires new employees and thus the organization’s payroll system
gets affected.

6
PROJECT MANAGEMENT
Supply chain system: Due to the up gradation from XP to windows 16, number of
hardware as well as software is required by the organization and thus the supply chain system of
the organization gets affected.
7. Specific Exclusion from scope
The exclusion from the scope of the project is provided in the table below:
 Up gradation of various network devices
 Up gradation of various application servers
 Upgrading the database of the organization
8. Implementation Plan
Name Fixed Cost Actual Cost Remaining
Cost
Cost Baseline Cost Cost
Variance
Software
Development
$0.00 $0.00 $475.00 $475.00 $0.00 $475.00
Software
requirements
$0.00 $0.00 $760.00 $760.00 $0.00 $760.00
Design $0.00 $0.00 $1,355.00 $1,355.00 $0.00 $1,355.00
Development $0.00 $0.00 $495.00 $495.00 $0.00 $495.00
Testing $0.00 $0.00 $180.00 $180.00 $0.00 $180.00
Unit testing $0.00 $0.00 $810.00 $810.00 $0.00 $810.00
Training $0.00 $0.00 $560.00 $560.00 $0.00 $560.00
Documentation $0.00 $0.00 $450.00 $450.00 $0.00 $450.00
Pilot $0.00 $0.00 $385.00 $385.00 $0.00 $385.00

7
PROJECT MANAGEMENT
Deployment $0.00 $0.00 $385.00 $385.00 $0.00 $385.00
Post
implementation
review
$0.00 $0.00 $175.00 $175.00 $0.00 $175.00
9. High-level budget and timeline/ schedule
9.1 Budget of the project
The budget that is required for completing the up gradation from XP to Windows 16 is
around $ 86,590. It is identified that the budget that is needed for completing the project
activities by the project stakeholders is around $ 46,590. In addition to this, the remaining budget
is utilized for other project expenses. The tables below reflect the budget that is required in the
project.
Budget for completing project with the help of project stakeholders
Resources
Working hours
(hrs)
Number of resources
required
Standard rate per
hour ($ )
Cost of the
Resources ($)
Project
planner
21 5
40 4200
Project
manager
33 2
45 2970
Analyst 11 10 40 4400
Developer 11 12 45 5940
Tester 33 10 30 9900
Trainer 16 8 35 4480
Technical
communica
tors
15 7
30 3150
Deploymen
t team
22 15
35 11550
Total ($) 46590

8
PROJECT MANAGEMENT
Budget for other resources
Material resources $25,000
Others $15,000
Total budget calculation
Resources Budget ($)
Material 25,000
Human resource 46590
Others 15,000
Total budget ($) 86,590
9.2 Schedule of the project
Task Name Duration Start Finish
A single-operator business is upgrading from XP 17.88 days Fri 11/24/17 Tue 12/19/17

9
PROJECT MANAGEMENT
to Windows 2016
Software Development 1.13 days Fri 11/24/17 Mon 11/27/17
Scope 2 hrs Fri 11/24/17 Fri 11/24/17
Determining project scope 3 hrs Fri 11/24/17 Fri 11/24/17
Securing project sponsorship 1 hr Fri 11/24/17 Fri 11/24/17
Defining preliminary resources 1 hr Fri 11/24/17 Fri 11/24/17
Securing core resources 2 hrs Fri 11/24/17 Mon 11/27/17
Milestone 1: Completion of scope 0 hrs Mon 11/27/17 Mon 11/27/17
Software requirements 1.88 days Mon 11/27/17 Tue 11/28/17
Conducting requirement analysis 3 hrs Mon 11/27/17 Mon 11/27/17
Drafting preliminary specifications of software 1 hr Mon 11/27/17 Mon 11/27/17
Developing preliminary budget 2 hrs Mon 11/27/17 Mon 11/27/17
Reviewing budget with the help of the team 3 hrs Mon 11/27/17 Tue 11/28/17
Feedback on different software specification 1 hr Tue 11/28/17 Tue 11/28/17
Developing proper delivery timeline 2 hrs Tue 11/28/17 Tue 11/28/17
Obtaining approvals for proceeding 1 hr Tue 11/28/17 Tue 11/28/17
Securing required resources 2 hrs Tue 11/28/17 Tue 11/28/17
Milestone 2: Completion of analysis 0 hrs Tue 11/28/17 Tue 11/28/17
Design 2.25 days Wed 11/29/17 Fri 12/1/17
Reviewing the various software specifications 3 hrs Wed 11/29/17 Wed 11/29/17
Developing functional specifications 4 hrs Wed 11/29/17 Wed 11/29/17
developing prototype as per different functional 5 hrs Wed 11/29/17 Thu 11/30/17

10
PROJECT MANAGEMENT
specification
Reviewing various functional specifications 2 hrs Thu 11/30/17 Thu 11/30/17
Incorporating feedback into different functional
specifications
3 hrs Thu 11/30/17 Fri 12/1/17
Obtaining approval for proceeding 1 hr Fri 12/1/17 Fri 12/1/17
Milestone 3: Designing completion 0 hrs Fri 12/1/17 Fri 12/1/17
Development 1.38 days Fri 12/1/17 Mon 12/4/17
Reviewing functional specifications 3 hrs Fri 12/1/17 Fri 12/1/17
Identifying various modular design parameters 2 hrs Fri 12/1/17 Fri 12/1/17
Assigning staff for development 2 hrs Fri 12/1/17 Mon 12/4/17
Developing code 3 hrs Mon 12/4/17 Mon 12/4/17
Developer testing 1 hr Mon 12/4/17 Mon 12/4/17
Milestone 4: Development completion 0 hrs Mon 12/4/17 Mon 12/4/17
Testing 0.75 days Mon 12/4/17 Tue 12/5/17
Developing unit testing 4 hrs Mon 12/4/17 Tue 12/5/17
Developing integration testing plan 2 hrs Tue 12/5/17 Tue 12/5/17
Unit testing 3.38 days Tue 12/5/17 Fri 12/8/17
Reviewing modular code 2 hrs Tue 12/5/17 Tue 12/5/17
Testing component modules for product
specifications
1 hr Tue 12/5/17 Tue 12/5/17
Identifying anomalies 3 hrs Tue 12/5/17 Wed 12/6/17
Modifying code 3 hrs Wed 12/6/17 Wed 12/6/17

11
PROJECT MANAGEMENT
Re-testing modifying coding 5 hrs Wed 12/6/17 Thu 12/7/17
Unit testing completion 3 hrs Thu 12/7/17 Thu 12/7/17
Integration testing 2 hrs Thu 12/7/17 Thu 12/7/17
Testing module integration 2 hrs Thu 12/7/17 Thu 12/7/17
Identifying anomalies to specifications 3 hrs Fri 12/8/17 Fri 12/8/17
Modifying code 1 hr Fri 12/8/17 Fri 12/8/17
Res-testing modified code 2 hrs Fri 12/8/17 Fri 12/8/17
Milestone 5:Integration testing completion 0 hrs Fri 12/8/17 Fri 12/8/17
Training 2 days Fri 12/8/17 Tue 12/12/17
Developing proper training specifications for
the end users
3 hrs Fri 12/8/17 Mon 12/11/17
Developing various specifications for helpdesk
support
2 hrs Mon 12/11/17 Mon 12/11/17
Identification of training delivery methodology 3 hrs Mon 12/11/17 Mon 12/11/17
Development of training materials 1 hr Mon 12/11/17 Mon 12/11/17
Usability study training is conducted 2 hrs Mon 12/11/17 Tue 12/12/17
Finalizing training materials 3 hrs Tue 12/12/17 Tue 12/12/17
Developing proper training mechanism 2 hrs Tue 12/12/17 Tue 12/12/17
Milestone 6:Completion of training
materials
0 hrs Tue 12/12/17 Tue 12/12/17
Documentation 1.88 days Tue 12/12/17 Thu 12/14/17
developing help specification 3 hrs Tue 12/12/17 Wed 12/13/17

12
PROJECT MANAGEMENT
developing help system 2 hrs Wed 12/13/17 Wed 12/13/17
Reviewing help documentation 2 hrs Wed 12/13/17 Wed 12/13/17
Incorporate feedback of help documentation 1 hr Wed 12/13/17 Wed 12/13/17
Developing user manual specifications 1 hr Wed 12/13/17 Wed 12/13/17
Developing user manuals 2 hrs Wed 12/13/17 Thu 12/14/17
Reviewing user documentation 1 hr Thu 12/14/17 Thu 12/14/17
Incorporating feedback of user documentation 3 hrs Thu 12/14/17 Thu 12/14/17
Milestone 7:Completion of documentation 0 hrs Thu 12/14/17 Thu 12/14/17
Pilot 1.38 days Thu 12/14/17 Fri 12/15/17
Identifying testing group 3 hrs Thu 12/14/17 Thu 12/14/17
Developing software delivery method 2 hrs Fri 12/15/17 Fri 12/15/17
Installing software 2 hrs Fri 12/15/17 Fri 12/15/17
Obtaining user feedback 3 hrs Fri 12/15/17 Fri 12/15/17
Evaluating testing information 1 hr Fri 12/15/17 Fri 12/15/17
Milestone 8:Pilot completion 0 hrs Fri 12/15/17 Fri 12/15/17
Deployment 1.38 days Mon 12/18/17 Tue 12/19/17
Determining strategy of final deployment 1 hr Mon 12/18/17 Mon 12/18/17
Developing methodology of deployment 3 hrs Mon 12/18/17 Mon 12/18/17
Securing deployment of resources 2 hrs Mon 12/18/17 Mon 12/18/17
Training support staff 2 hrs Mon 12/18/17 Mon 12/18/17
Deploying software 3 hrs Tue 12/19/17 Tue 12/19/17
Milestone 9: Completion of deployment 0 hrs Tue 12/19/17 Tue 12/19/17

13
PROJECT MANAGEMENT
Post implementation review 0.5 days Tue 12/19/17 Tue 12/19/17
Document lessons learned 2 hrs Tue 12/19/17 Tue 12/19/17
Distributing team members 1 hr Tue 12/19/17 Tue 12/19/17
Creating software maintenance team 1 hr Tue 12/19/17 Tue 12/19/17
Milestone 10: Completion of post
implementation review
0 hrs Tue 12/19/17 Tue 12/19/17