ITT700 : PM

Project Scope Plan

AggiesSync

Data Backup Systems

Members :1) Ammar Abdulmughni2) Aaron Scales3) Nakiea Bell4) Timothy Alligood5) Allen McLean

Date: 10/23/2016

North Carolina A&T state universitySchool of Science – Information Technology

2016 - 2017

Contents1.0 Introduction:..............................................................................................................................................................3

2.0 Requirements Document:..........................................................................................................................................3

2.1 Project details:.......................................................................................................................................................3

2.2 Roles and responsibilities:....................................................................................................................................3

3.0 Detailed Project Scope: (Define Scope):..................................................................................................................4

3.1 The project scope statement:.................................................................................................................................4

3.2 Project justification...........................................................................................................................................5

3.3 The system will include the following:.............................................................................................................5

3.4 Project Description:..........................................................................................................................................5

3.5 Project Deliverables:.........................................................................................................................................5

3.5 Project Objectives:............................................................................................................................................5

3.6 Cost Objectives:................................................................................................................................................5

3.8 Constraints........................................................................................................................................................6

3.9 Assumptions:.....................................................................................................................................................6

4.0 Work Breakdown Structure (Create WBS):.............................................................................................................6

5.0 Scope Verification (Verify Scope):..........................................................................................................................8

6.0 Scope change and control process: (Scope control):................................................................................................8

7.0 Design Document:....................................................................................................................................................9

7.1 General Overview:................................................................................................................................................9

7.2 Scope:....................................................................................................................................................................9

7.3 Website Characteristics:........................................................................................................................................9

The website will include:........................................................................................................................................9

The website will not include:....................................................................................................................................10

7.4 The website development tools:..........................................................................................................................10

7.5 Interfaces and screenshots:.................................................................................................................................10

1.0 Introduction:Scope Management is the collection of processes which ensure that the project includes all the work required to complete it while excluding all work which is not necessary to complete it. The Scope Management Plan details how the project scope will be defined, developed, and verified. It clearly defines who is responsible for managing the projects’ scope and acts as a guide for managing and controlling the scope.

Project Scope management follows five step process; Project Scope Management follows a five step process; Collect Requirements, Define Scope, Create WBS, Verify Scope, and Control Scope.

This project is for designing, implementing and testing a new backup data system which will be used to store, backup, recover company’s database and improve data storage systems. This will include the design of the new network, all hardware equipment. No external resources or outsourcing are anticipated for this project.

2.0 Requirements Document: 2.1 Project details:

Project Data backup Systems ( AggiesSync)Project Sponsor

Nakiea Bell

Project manager

Timothy Alligood

Start Date 01-01-2016Completion Date

12-01-2016

2.2 Roles and responsibilities:The project Manager, Sponsor and team will all play key roles in managing the scope of this project. As such, the project sponsor, manager, and team members must be aware of their responsibilities in order to ensure that work performed on the project is within the established scope throughout the entire duration of the project. The table below defines the roles and responsibilities for the scope management of this project.

Name Role ResponsibilitiesNakiea Bell Sponsor - Approve or deny scope change requests as

appropriate- Evaluate need for scope change requests- Accept project deliverables

Timothy Alligood Project Manager

- Measure and verify project scope- Facilitate scope change requests- Facilitate impact assessments of scope change

requests- Organize and facilitate scheduled change

control meetings- Communicate outcomes of scope change

requests- Update project documents upon approval of all

scope changesAmmar Team Lead - Measure and verify project scope

- Validate scope change requests- Participate in impact assessments of scope

change requests- Communicate outcomes of scope change

requests to team- Facilitate team level change review process

Aaron Scales Team Member - Participate in defining change resolutions- Evaluate the need for scope changes and

communicate them to the project manager as necessary

Table 1.1, Scope Management Roles and Responsibilities

3.0 Detailed Project Scope: (Define Scope):3.1 The project scope statement:This project includes the design, developing, implementing and testing of a new data backup system for the company’s Database and digitally archived data. The deliverables for this project are a completed, reliable data storing, recovering, back up data systems with the flexibility to choose different ways and methods of data backup and storage as well as restoring data. Also, it can be modified in the future to expand the capacity of data storage without having the difficulties of replacing old hardware with a new or to worry about the high cost along with that change. The project will be accepted once the system has been tested successfully in each department and has been shown to be compatible with the current company’s network infrastructure, hardware and equipment. This project doesn’t include ongoing operations and maintenance of the hardware. Additionally, the project is not to exceed 365 days in durations or $450,000 in spending.

3.2 Project justification:

1- To contain current and future IT cost.

2- Increase opportunity for backup system.

3- Reduce problems found within IT

3.3 The system will include the following:

1- Provide secure storage for data assets critical to the work flow of official  university business

2- Prevent loss of data in the case of accidental deletion / corruption of data,  system failure, or disaster

3- Permit timely restoration of archived data in the event of a disaster or system  failure This policy applies to all computers, both mobile and desktop, owned by the Library

4- Specific locations will be automatically backed up (e.g., My Documents, Desktop,  Bookmarks)

5- Maintaining a versioned history of data

6- Personal data such as photos, videos, music, non‐brown e‐mail accounts, etc. 

7- backup system is utilized to retain data for 6 weeks or 42 days.  A combination of incremental and full backups is executed on the dataset.  A full backup is  performed every Friday with incremental backups thereafter.

3.4 Project Description:

Back up Support system for data and storage

3.5 Project Deliverables:

Back up Support System for data and storage

3.5 Project Objectives:

Increase customer satisfaction. Increase amount of data and storage that can be backed up. Reduce amount if IT related problems.

3.6 Cost Objectives:

Project not to exceed $450,000 in expense 3.7 Schedule Objectives:

Designated IT back support system within 12 months

3.8 Constraints:

Resource availability, Budget, and time

3.9 Assumptions:Assumptions for this project are that support will be provided by the project sponsor and all department managers and that adequate internal resources are available for the successful completion of this project.

4.0 Work Breakdown Structure (Create WBS):In order to effectively manage the work required to complete this project, it will be subdivided into individual work packages which will not exceed 40 hours of work. This will allow the Project Manager to more effectively manage the project’s scope as the project team works on the tasks necessary for project completion. The project is broken down into three phases: the design phase; the installing phase; and the testing phase. Each of these phases is then subdivided further down to work packages which will require no more than 40 hours of work and no less than 4 hours of work (see WBS structure below):

Figure 1.1, Work Breakdown Structure (WBS)

New data backup system

1.1 The desgin pahse

1.1.2 Second design Phase

1.1.1 First Design Phase

1.2 The installing phase

1.2.1 Installing Task #1

1.2.3 Installing Task #3

1.3 The testing phase

1.3.1 Testing task#1

1.3.2 Testing Task #2

In order to more clearly define the work necessary for project completion the WBS Dictionary is used. The WBS Dictionary includes an entry for each WBS element. The WBS Dictionary includes a detailed description of work for each element and the deliverables, budget and resource needs for that element. The project team will use the WBS Dictionary as a statement of work for each WBS element.

Level WBS Code

Element Name Description of Work Deliverables Budget Resources

1 1 Data Backup System

Data backup and restoring systems

Reliable data backup, storage systems

$450,000 Project Manager, sponsor

2 1.1 The design phase

Designing the network structure, blue print of the network, Specification of all hardware requirement.

Clear network blue print, required hardware for the network

$ 50,000 Team Leader, Project manager, sponsor

2 1.2 The installing phase

Gathering all resources, we need for installation (Hardware, equipment, software)

Make all sources for installation ready and available

$50,000 Team members, Team Leader, Project manager

2 1.3 The testing phase

Make a plane of performing a testing systems (e.g. schedule a backup and recover it and them compare to the original one, evaluate results)

A solid plan for resting the backup.

$50,000 Team Leader, Project manager

3 1.1.1

First design phase

Design all outbound connections (WAN)

A blue print and a plan of what will be used for outside connection.

$50,000 Team Leader, Project manager, Sponsor

3 1.1.2

Second design phase

In the location, install all required hardware ( routers, wiring, servers)

The location is ready with all hardware instllations

$50,000 Team Leader, Project manager

3 1.2.1

Installing task #1

Remotely setup all systems and roles that goes on server

Make server ready with all data backup systems

$50,000 Team members, Team Leader, Project manager

3 1.3.1

Testing task #1

Test a dummy data to make sure of functionality

Dummy version or trial version to test the data backup system

$50,000 Team Leader, Project manager

4 1.2. Installing Install all required All terminals $50,000 Team

3 Task #2 systems on the clients’ workstations (Terminals)

have successful communications with the data backup server

members, Team leader, Project Manager

4 1.3.2

Testing Task # 2

Real life test, in the location

A real life testing example to make sure the readiness of the systems

$50,000 Team Leader, Project manager, Sponsor

Table 1.2, WBS Dictionary

5.0 Scope Verification (Verify Scope):As this project progresses the Project Manager will verify interim project deliverables against the original scope as defined in the scope statement, WBS and WBS Dictionary. Once the Project Manager verifies that the scope meets the requirements defined in the project plan, the Project Manager and Sponsor will meet for formal acceptance of the deliverable. During this meeting the Project Manager will present the deliverable to the Project Sponsor for formal acceptance. The Project Sponsor will accept the deliverable by signing a project deliverable acceptance document. This will ensure that project work remains within the scope of the project on a consistent basis throughout the life of the project.

6.0 Scope change and control process: (Scope control):We this stage we need to go through the following checklist:1- MOV: Does the project clearly define the MOV?2- Deliverables: Are all the deliverables tangible and verifiable? Do they support the project’s MOV?3- Quality Standards: Are all controls in place to ensure that the work was not only completed, but completed to meet specific standards?4- Milestones: Are milestones defined for each deliverable?5- Review and acceptance: Are both sides clear in their expectations? The project’s scope must be reviewed and accepted by the project stakeholders.

The Project Manager and the project team will work together to control of the scope of the project. The project team will leverage the WBS Dictionary by using it as a statement of work for each WBS element. The project team will ensure that they perform only the work described in the WBS dictionary and generate the defined deliverables for each WBS element. The Project Manager will oversee the project team and the progression of the project to ensure that this scope control process if followed.

If a change to the project scope is needed the process for recommending changes to the scope of the project must be carried out. Any project team member or sponsor can request changes to the project scope. All change requests must be submitted to the Project Manager in the form of a

project change request document. The Project Manager will then review the suggested change to the scope of the project. The Project Manager will then either deny the change request if it does not apply to the intent of the project or convene a change control meeting between the project team and Sponsor to review the change request further and perform an impact assessment of the change. If the change request receives initial approval by the Project Manager and Sponsor, the Project Manager will then formally submit the change request to the Change Control Board. If the Change Control Board approves the scope change the Project Sponsor will then formally accept the change by signing the project change control document. Upon acceptance of the scope change by the Change Control Board and Project Sponsor the Project Manager will update all project documents and communicate the scope change to all project team members stakeholders.

7.0 Design Document:www.aggiessync.wordpress.com

7.1 General Overview:

This design document is to explain our website that we are creating for our services. AggiesSync website will introduce the services to our clients or any potential clients.

7.2 Scope:The web design document will demonstrate how the web will provide our clients latest news and services. Also, the new clients can be introduced to our services.7.3 Website Characteristics:

1- To keep our clients updated and posted of our new products and services.2- To reach out to the new customers and introduce them to the nature of our business.3- To provide our customers of the new feature of security to protect their data.4- To provide our clients of scalable and easy tool to reach our techs for support (e.g.

opening a support ticket)

The website will include:a. Our clients page

b. Our services page

c. About us page

d. Contact us page

e. Security policies

f. Clients can create support tickets

g. Clients can be posted of our news and latest services.

The website will not include:a) E-commerce

b) User or clients’ login

c) Performance monitoring and reporting

d) Software & drivers downlaod

e) Training lessons

7.4 The website development tools:- The website is mainly designed and hosted by WordPress.com.- We used some of the ready programmed widgets in WordPress.- In the future we can add some of PHP pages, HTML pages and Java applets.

7.5 Interfaces and screenshots: Screenshot 1:

Screenshot 2:

Our servicesContact UsAbout

HomeOur clientsSecurity Policies