Running head: PROJECT PLAN-HOPKINS
1
Project Plan-Hopkins
Vanessa McAndrew
MBA- FP 6231 U06A2
Executive Summary, Evaluation, and Plan
Capella University
Professor
Gerald Huff
April 7, 2018
PROJECT PLAN-HOPKINS
2
Table of Contents
1.Executive Summary
...................................................................................................................................
3
2.Project Charter
.........................................................................................................................................
5
3.Project Scope Statement
.........................................................................................................................
10
4.Cost Estimate
..........................................................................................................................................
17
5.Risk Matrix
.............................................................................................................................................
22
6.Project Evaluation
..................................................................................................................................
27
PROJECT PLAN-HOPKINS
3
Executive Summary
The project entails coming up with the entire project plans, which include the milestones, tasks,
schedules, staffing, deliverables as well as forecasted costs for software development project. In
this project, the primary idea is to analyze organizational setting of Hopkins that has significant
software needs and then come up with the essential plans. Hopkins has complicated
organizational structure and the situation in which the organization operates is unclear. Through
reviewing the existing facts, collecting the required information, doing different playing
interviews, executing analysis of requirements and then estimating the schedules and costs, the
project will proceed to collect information required to develop the baseline project plans for the
software development. Oil and gas audit remains a competitive area that must adopt latest modes
of technology or remain out. The need to implement the software is to institute a realistic way of
addressing and helping mitigate the risk and give developers a chance of coming up with first-
rate system that meets the needs while withholding the stress. The files at Hopkins are manually
being done and there is need to have electronic filing and organization, index and catalogue
completed evaluations. The business has not had streamlined tasks and integration of the same
tasks. The software developed need to be in a position to streamline the task of doing oil and gas
economics reservoir analysis to ultimately remain competitive. The project scope entails
development of a new software, integration of the three models to have one seamless and
effective software and re-aligning roles of individuals in the organization. The project is to be
started on 15th May, 2018 and is expected to be completed in 90 days. During the period,
presentation of initial document will be done on 03.24. 2018 then second amended version
availed on 04.27.2018. Lastly, the submission of the paper will be done on 05.15.2018 and then
project is expected to be complete by 15th August, 2018. The project is expected to face several
PROJECT PLAN-HOPKINS
4
risks, which include vandalism, access of site, topography, political climate, and availability of
resources, defective design, costs of tests, samples, and productivity labor. The inherent risks will
be communicated as communication is the tool used to make the stakeholders understand the risk
their project is liable to. In this project, communication will be enhanced by communicating the
different risks and their priority to the project over time. This will assist in contributing
positively to the overall project success. The risk communication will involve outlining the
differences in the risks in the priority they are all assigned. This will also enhance the ability of
