Implementing Cloud Computing for Increased Storage Space in Retail Store

The retail store is implementing cloud computing for increased storage space and faster computing methods. This service provides secure storage for transaction files and important documents, improved accessibility, and emergency backup. The project plan includes delivery of SOW, project plan approval, successful data conversion and migration, and project delivery.

Statement of Work Student Name:
Project Summary
Service Description
Deliverables
The major deliverables of this project are-
Deliverable 1 Delivery of SOW
Deliverable 2 Project Plan Approval
Deliverable 3 Successful Data Conversion and Migration
Deliverable 4 Project Delivery
The retail store utilizes ERP for the business and as the business is growing, there is a need of increased
storage space. This is the reason why the store is thinking of implementing cloud computing in their
business.
The service of cloud computing requires several additional hardware and software for implementation. The
storage of cloud provides increased storage area along with faster and easier computing methods. The store
can store the files of transaction and several other important documents easily and securely. The store can
gain increased accessibility to the files and protect the sensitive files. The store can save huge amount of
capital that is spent on the securing of the files. The company is relieved of the burden of maintaining and
monitoring of data of the company. The emergency backup of the files of the company can be easily done
and the access to these files can be improved with cloud storage.

Deliverables Schedule
The delivery schedule of the project is represented in the table below-
WBS Task Name Duration Start Finish
0 Cloud Implementation 81 days Mon 08-10-18 Mon 28-01-19
1 Project Starts 0 days Mon 08-10-18 Mon 08-10-18
2 Project Planning 9 days Mon 08-10-18 Thu 18-10-18
2.1 Requirements Gathering 2 days Mon 08-10-18 Tue 09-10-18
2.2 Understanding the Project
Specifications 3 days Wed 10-10-18 Fri 12-10-18
2.3 Development of Statement of Work 3 days Mon 15-10-18 Wed 17-10-18
2.4 Sharing Document with the Clients 1 day Thu 18-10-18 Thu 18-10-18
2.5 M1: Delivery of SOW 0 days Thu 18-10-18 Thu 18-10-18
3 Project Initiation 3 days Fri 19-10-18 Tue 23-10-18
3.1 Development of Project Plan 3 days Fri 19-10-18 Tue 23-10-18
3.2 Estimation of Project Budget 2 days Fri 19-10-18 Mon 22-10-18
3.3 Sharing Project Plan with clients for
Approval 1 day Tue 23-10-18 Tue 23-10-18
3.4 M2: Project Plan Approval 0 days Tue 23-10-18 Tue 23-10-18
4 Project Implementation 57 days Wed 24-10-18 Thu 10-01-19
4.1 Choosing the accurate cloud based
Approach 7 days Wed 24-10-18 Thu 01-11-18
4.2 Software Coding 15 days Fri 02-11-18 Thu 22-11-18
4.3 Testing the system 15 days Fri 23-11-18 Thu 13-12-18
4.4 Data Migration from old system to
new system 20 days Fri 14-12-18 Thu 10-01-19
4.5 M3: Successful Data Conversion and
Migration 0 days Thu 10-01-19 Thu 10-01-19
5 Project Closure 12 days Fri 11-01-19 Mon 28-01-19
5.1 Project Evaluation 5 days Fri 11-01-19 Thu 17-01-19
5.2 Payment Completion 2 days Fri 18-01-19 Mon 21-01-19
5.3 Resource Release 3 days Tue 22-01-19 Thu 24-01-19
5.4 Client Sign Off 2 days Fri 25-01-19 Mon 28-01-19
6 M4: Project Ends 0 days Mon 28-01-19 Mon 28-01-19
The Gantt Chart of the project is represented in the following picture-

Figure 1: Representing the Gantt Chart of the project
(Source: Generated by Author using MS project)
Period of Performance:
The duration of the project is represented in the following table-
Task Name Duration
Cloud Implementation 81 days
Project Starts 0 days
Project Planning 9 days
Requirements Gathering 2 days
Understanding the Project Specifications 3 days
Development of Statement of Work 3 days
Sharing Document with the Clients 1 day

M1: Delivery of SOW 0 days
Project Initiation 3 days
Development of Project Plan 3 days
Estimation of Project Budget 2 days
Sharing Project Plan with clients for Approval 1 day
M2: Project Plan Approval 0 days
Project Implementation 57 days
Choosing the accurate cloud based Approach 7 days
Software Coding 15 days
Testing the system 15 days
Data Migration from old system to new system 20 days
M3: Successful Data Conversion and Migration 0 days
Project Closure 12 days
Project Evaluation 5 days
Payment Completion 2 days
Resource Release 3 days
Client Sign Off 2 days
M4: Project Ends 0 days
Payment Schedule
The payment will be provided to the contractors after the completion of each deliverables.
Sub-Contractors
The sub-contractors of the project are supplier of the required software and the hardware for the
implementation of the cloud services.
Representatives
The representatives in this project are the representatives of the client. The representatives of the project
manager are also associated with this project.
SUB SECTIONS
I. Risks and Assumptions: The risks that are connected with the project are that the escalation of the cost
of the project due to poor cost estimating accuracy and the creep of the scope. The schedule risk that is
associated with the project is that the implementation activity can take longer than expected. The
slippages in the schedule majorly consists of the increase in costs and the delay in the receipt of the
benefits of project with the probable loss in the competitive advantage. The risk of performance that are
associated with the project is the consistent results with the specifications of the project.
The assumption that is considered is that the project will be completed within the provided time period
in the budget provided and the time that is allocated for the project.

II. Stakeholders: The stakeholders of the project are the project leader, the senior management, the
members of the team of the project, the customer of the project, the managers of resource, line
managers, group of user of the product, the tester of the project, project subcontractors and project
consultants.
III. Applicable Standards: The project of application development have to operate in agreement with the
standards of enterprise architecture, the principles, methods and the processes. The documentation of the
outputs in compliance with the established documentation process. The project team must confirm that
the contract programmer should obey the quality standards.
IV. Acceptance Criteria: the application will be accepted when the old files are safely and securely stored
in the cloud storage after encryption. The technology will be accepted after the documents consisting of
the transactions of the store has to be stored securely.
V. Special Requirements or out of scope items: the special requirement that is essential in the project is
the requirement gathering of the customers.