Project Scope Statement - Centralize It Company’s Programs

PROJECT SCOPE STATEMENT

Justification and Purpose

The purpose of this project is to centralize IT Company’s programs onto a common management platform in order to improve management, prioritization, and resource allocation of its numerous programs. As a small regional business, IT Company has historically been challenged with limited resources for managing its many client programs. As a consequence, some programs have exceeded their budget, experienced delays, and/or have not sufficiently met their deliverables. The successful implementation of this project is estimated to reduce IT Company’s cost schedule delays and overruns by ~30%.

Description

The scope of this particular project is to plan, design, create, and implement a database tool that IT Company’s programs can be efficiently managed with.  Each program will include a virtual dashboard with metrics integral to providing a consistent system in which to measure a program’s status. Program dashboards typically contain budget data, schedules, assigned resources, risks, and milestones for each program. The scope of this project will include all planning, requirements, design, development, and implementation of the database tool.

High-Level Requirements

The database tool has been approved to meet a business need for IT Company. These high-level requirements have been identified for the project:

• Database platform with permissions granted to all staff
• Accessible both from the office or off site
• Program tool to ensure all program dashboards are consistent
• Ability to maintain tool internally

Boundaries

The boundaries for this project include all work tasks associated with designing, building, and implementing the database tool for IT Company.

Strategy

This area describes the stratagem the project team will be executing in order to complete the project. Depending on the complexity and size of the project, strategies can vary widely. As the number of stakeholders, deliverables, and complexity rises, the strategy can become more complicated to plan.

Deliverables

This area describes the deliverables that will be produced upon successful completion of the project. If all of the deliverables are not met, then the project will not be considered successful. It is the project manager’s direct responsibility to ensure the completion of these deliverables.

Acceptance Criteria

The acceptance criteria is both qualitative and quantitative. Acceptance criteria must be met in order to achieve project success:

1. Meet deliverables within scheduled time and budget constraints.
2. Reduce budget overruns and schedule delays by ~30%.
3. Improve IT Company’s resource allocation ability.
4. Accomplish an overall improvement of performance.

Constraints

These are the constraints that have been identified for this project:

1. Project must be completed by close of business on December 31, 2016.
2. Project must be completed within budget allowance.
3. Database tool must be compatible with existing hardware/software, as no new purchases will be authorized.

Assumptions

Several assumptions have been identified for the project. During the planning cycle it is imperative to identify and mitigate any risk associated with the following assumptions:

1. Workgroup is capable of producing a standard operating procedure manual or guides.
2. There is enough staff working on this project to complete it by December 31, 2016.
3. The project has the support of senior management throughout all departments.

Cost Estimate

The project’s estimated costs are detailed in the next section. As the project proceeds and any additional costs become known, this cost estimate will be updated and promulgated to stakeholders in a timely manner.

Cost Benefit Analysis

A cost benefit analysis has been performed for the project. Successful completion of this project will provide considerable benefits to IT Company. It is vital that stakeholders fully understand these benefits, as well as the importance of the completion of the project. The hypothetical table below illustrates a net benefit of $31,000 over one year after successful completion of the project. This is a total benefit of $206,000 if nothing is changed and schedule delays, cost overruns, and poor allocation of resources are allowed to continue.