Running head M7A1 - PROJECT MANAGEMENT PLAN1M7A1 - PROJECT.docx

Running head: M7A1 - PROJECT MANAGEMENT PLAN
1
M7A1 - PROJECT MANAGEMENT PLAN
2
M7A1 - Project Management Plan
[Student Name]
IT 390
Professor Charles Snead
[Current Date]
Project Management Plan
Project Name: [name of project]
Project Description: [one paragraph description of the project]
Business Justification: [one paragraph describing the business
need for the project]
Project Manager and Key Stakeholders
Name
Role
Position
Contact Information

Required Deliverables:
· [the deliverables, in bullet form]
Key Definitions and Acronyms
· [project-specific definitions of terms and acronyms, in bullet
form]
Project Staffing:
· [staffing requirements for the team]
Organizational Charts
· [org chart of stakeholders and team members]

Project Responsibilities:
· [responsibilities of key stakeholders, in bullet form]
Management Objectives:
· [management objectives, in bullet form]
Project Controls:
· [controls used to manage scope and change, in bullet form]
Top 3 Risk Assessment:
· [See page 459 of the textbook] Scope Management Section
Key Deliverables:
· [deliverables and expected dates, in bullet form]
Work Packages:
· [work packages from WBS needed to produce the deliverables,
in bullet form]
Quality Baseline
· [you will need metrics that are measurable. For example,
stating that something must be faster is not measurable; stating
that something must be 10% faster than the current process
is.]Project Schedule Section
Summary schedule:
· [high level schedule of milestones and key deliverables, in
bullet form]
Budget
Summary Budget:
Cost Estimate for Dave's Bar & Grill POS System
# Units/Hrs.
Cost/Unit/Hr
Subtotals
WBS Level 2 Totals
% of Total
1. Project Management Costs

[project manager]
[development team]
[other stakeholders]
2. Hardware

3. Software
4. Testing (10% of total hardware and software costs)

5. Training and Support
6. Reserves (20% of total estimate)
Total project cost estimate

Choose a topic from ‘http://behaviouralfinance.net/’.
A. Write a 6 to 8 page paper on the subject.
B. Construct a 10-minute presentation and present your topic
to the class.
C. All assignments are due on the last day of the course.
Outline of a ‘research project’:
Section 1: Theory
In section 1 of your document, you should examine where,
when, and by who your particular research topic was conceived
and what it ‘looked’ like at that time. Your research should
include the seminal work that laid the foundation for your topic.
Section 2: Present
In section 2 of your document, you should examine how the
theoretical base of your topic has evolved over time. The
objective here is to bring your topic to the present and engage
in research related to recent articles published on this topic.
Section 3: Application
In section 3 of your document, you should find some way to
apply this theoretical base to a business case / scenario. How
does this topic affect us, influence us? How can we leverage our
knowledge of this topic to make better business decisions? Is
your topic ‘empirical’, can you construct an analysis to test it?
Student Name: Joseph Moore
Project Name: New Software Development
1. Project Type
New Software Development- the purchasing business needs to
have long-term management preparation used for choosing,
approving and upgrading software programs such as commercial
off-the-shelf (COTS) and other software products which are
reusable. If a mixture of these constituents is increased in the
new systems, the demand continues to grow. The new software
management plan and COTS usually help to facilitate the

purchasing of new programs management of COTS and some of
the reusable software. The new COTS and reusable software
will provide the strategy that outline data management about
monitoring interdependency of software, tracking, choosing
specific features and documenting those choices. The reusable
software and COTS presented in this project functions as a
guide for how to accomplish new software components and
COTS in a complex system (Anderso,Smith and Ward, 2007).
2. Purpose
The purpose of this project is help in identifying the techniques
and collaborative processes in handling the new software
components, and to address the risks and other issues. Some of
the actions that must be taken to address the risk and issues
include identification of the components that can be shared
across the software system and encourage their use
(Anderso,Smith and Ward, 2007). Create COTS and software
component estimation process that helps to address
interoperability, other principles recognized in the Component
Assessment Standards and documented in the strategies of
Software Development Plan. Create COTS and software
tracking system which includes constituent information from
COTS dealers who often combine other components of COTS
into their products. Finally, enable the evolution of reusable
software component that is steady and dependable with curved
development model.
3. Scope
This project seeks to justify the new development on the
application of COTS solution. It also provides introductory
information about COTS and new software programs and
describes its relationship to other program plans
(Anderso,Smith and Ward, 2007). The COTS and new software
project planning applies to the business such as Unilever that
choose, assess and use software components. This includes
some of the techniques like tracking statement programs,
checking software interdependency, selecting exact features and
documenting those choices, assessing and alleviating the risks

related to COTS and new software component in a system. The
reusable software can be grouped into different categories of
components; some of them include Shareware, Commercial off-
the-shelf (COTS) and Government off-the-shelf (GOTS).
4. Goals and Deliverables
The main goals of the project include: to eliminate the baseless
production of similar but different software components which
are reusable across the organization and support the quantity
discounts if possible. Secondly is to describe strategies for the
program and approaches to managing and developing software
components and COTS, which provide an origin for supporting
roles and possesses (Anderso,Smith and Ward, 2007). Thirdly is
to provide a summary of roles of the program that are affected
by development plan and includes an overview of the operation
that supports the software plan strategies. Additionally, to
ensure software development plan is implemented by describing
the programs processes. Finally, to describe the activities that
exceeds the development of the systems and employs reusable
software components.
5. Required Resources
Resources are means used to achieve the objectives of the
project. The primary resource is people who have diverse skills
and five years’ experience in project management. They must
also be competent enough to carry out outstanding work.
Secondly, there is a need for adequate funds which helps the
project activities to run smoothly (Kerzner, 2013). The
equipment’s such as computers will also be required to keep
data collected during the project. Other materials include
notebook and pen. The availability of resources will give
freedom on completion of project activities. These resources I
gathered them at the beginning of the project.
References
Anderso, W., Smith, D., & Ward, M. C. (2007, October). COTS
and Reusable SoftwareManagement Planning: A Template
forLife-Cycle Management. Retrieved October 2015, from

software engineering institute:
https://resources.sei.cmu.edu/asset_files/TechnicalReport/2007_
005_001_14882.pdf
http://www.peterjoubert.com/resource-requirements/
Kerzner, H. R. (2013). Project management: a systems approach
to planning, scheduling, and controlling. John Wiley & Sons.
1
8
Project Scope Statement
New Soft
development
Joseph Moore
8 November 2015Introduction
This project is primarily designed to promote the significance of
new software development to the companies. The purchasing
business should possess’ long-term management preparation
used for choosing, approving and upgrading software programs
such as commercial off-the-shelf (COTS) and other software
products that are reusable. If a mixture of these constituents is
increased in the new systems, the demand continues to grow.
The new software management plan and COTS usually help to
facilitate the purchasing of new programs management of COTS
and some of the reusable software. The project addresses how
new COTS and reusable software will provide the strategy that
outline data management about monitoring interdependency of
software, tracking, choosing specific features and documenting
those choices. The reusable software and COTS presented in
this project functions as a guide for how to accomplish new
software components and COTS in a complex system (Anderso,

Smith, and Ward, 2007).Project Purpose and Justification
The objective of this research is to help in identifying the
techniques and collaborative processes in handling the new
software components and to address the risks and other issues.
The project also seeks to eliminate the baseless production of
similar but different software components which are reusable
across the organization and support the quantity discounts if
possible. It describes the strategies for the program and
approaches to managing and developing software components
and COTS, which provide an origin for supporting roles and
possesses. The project provides a summary of roles of the
program that are affected by development plan and includes an
overview of the operation that supports the software plan
strategies. Furthermore, it ensures software development plan is
implemented by describing the programs processes. Some of the
activities that must be taken to address the risk and issues
include identification of the components that can be shared
across the software system and encourage their use (Anderso,
Smith, and Ward, 2007).Scope Description
describes its relationship to other program plans (Anderso,
Smith, and Ward, 2007). The anticipated deliverables include a
new software program that needs to be written by exact
deadline. It should be delivered in numbered phases. The first
release will contain some new elements that will be present in
final product. The training program, since the software program
is new, there will be training design that tells the users how
training on new software will be developed. After a task
analysis, the training program is established and approved as
the final deliverables. Finally, the accounting program
processes are established to allow implementation of a program
that is being created. The hardware is ordered and tested, the
trainers are identified and implementation of new software
according to due dates.High Level Requirements

The work should be planned to utilize a project definition
document. The time spent on the planning of the project will
result in a reduction in cost and duration hence increases quality
over the time of the project. Define the procedures of project
management upfront. The procedure outlines all the resources
that should be used in the management of the project. This
include sections how the team will manage scope issues, risk,
and communications. Finally manage the work plan and monitor
the budget. Once the project has been properly planned the
execution of the work begins (Kerzner, 2013).Boundaries
This includes some of the techniques like tracking statement
programs, checking software interdependency, selecting exact
features and documenting those choices, assessing and
alleviating the risks related to COTS and new software
component in a system. The reusable software can be grouped
into different categories of components; some of them include
Shareware, Commercial off-the-shelf (COTS) and Government
off-the-shelf (GOTS).Strategy
The project team will use tradition approach. The strategy
assumes that the scope of the project and goals will remain
constant till the project ends. In this case, the project manager
will plan and identify resources for the project based on this
assumption. The tradition method lays down following stages:
1. Initiation of the project
2. Planning and designing the project
3. Monitoring and controlling of the project
4. Execution of the project
5. Completion of the project
Deliverables

1. A new software program that is written by the exact deadline,
this should be delivered in numbered phases. The first release
will contain some new elements that will be present in final
product.
2. The training program, since the software program is new,
there will be training design that tells the users how training on
new software will be developed. After a task analysis, the
training program is established and approved as the final
deliverables.
3. Finally, the accounting program processes will be established
to allow implementation of a program that is being created. The
hardware is ordered and tested, the trainers are identified and
implementation of new software according to due dates.
Acceptance Criteria
1. Improved information flow- this involves the flow
information of from one step to another
2. Improved flow of the process- this involves systems
improvement
3. Increased the quality of the product- this is the state of
achieving desired output.Constraints
1. Failure to manage projects with the unspecified schedule, the
project management imposes deadline and budget on any project
that creates major problems. When the project has to be finished
in time and has schedule, its quality can be compromised.
2. Secondly dependence on the functional management, this is a
major problem because project managers constantly work at the
mercy of resources and functional managers.
3. Finally, an exclusive methodology, the project management
forces the project manager to choose and follow methods be it
tradition or agile.Assumptions
1. Project schedule- this is a detailed description of the staffs

action steps needed in project management.
2. Personnel recruitment and training is essential for personnel
in the project team
3. Technical tasks- this is the availability of expertise and
required technology to achieve the specific action steps.
4. Support from top management- the top management should be
willing to provide necessary resources and authority of the
power of the project success.
5. Communication- entails the provision of data and proper
network to all key actors in the project management.
6. Troubleshooting- is the capacity to handle deviations from
the plan and handle unexpected crises.Risk Analysis and
Mitigation Strategy
Types of risks
1. System or product complexity, this is how the project is
complex and big
2. Team environment- the team makes an enormous difference
to the success of the project. This risk needs careful
consideration because it can break the project
3. Business project risk- if the project is moved to a new part
that has not been not tried or verified. The risk is greater
because it is about the aspect of the business not ending result.
Mitigation strategies
1. Restructure the project so as to minimize the impacts of early
decisions on downstream conditions. Decisions that eliminate

options and constrain future decisions should be reconsidered.
2. Stage the project so that it is always reviewed for no go
decisions discrete and identifiable points. These plans must be
constructed into front end plan.
3. Change the scope of the project, this should be either down
or top, at some future decision points. In the high-uncertainty
project, corrections may be necessary to improve the
information.Cost Estimate
Expense
Estimated Budget
Expended to Date
Estimate to Complete
Variance
Labor
$10000
7/11/2015
$11000
Internal
$7000
10/11/2015
$7500
$500
External
$3000
10/11/2015
$3500
$500
Software
$5000
22/11/2015
$5100
$100
Hardware

$6000
30/11/2015
$6200
$100
Other
$3000
12/12/2015
$3500
$500
Total
$24000
$$4200
$1800
References
PAGE
8
running head: project charter
1
Project Charter
< New Software Development >
Joseph Moore
1 November 2015

Project Charter
< New Software Development >
Project Manager: Joseph Moore
Anticipated Start Date: November 1 2015
Anticipated End Date: October 16, 2016
Project Summary
This project is primarily designed to promote the significance of
new software development to the companies. The purchasing
business should possess’ long-term management preparation
used for choosing, approving and upgrading software programs
such as commercial off-the-shelf (COTS) and other software
products which are reusable. If a mixture of these constituents
is increased in the new systems, the demand continues to grow.
The new software management plan and COTS usually help to
facilitate the purchasing of new programs management of COTS
and some of the reusable software. The project addresses how
new COTS and reusable software will provide the strategy that
outline data management about monitoring interdependency of
software, tracking, choosing specific features and documenting
those choices. The reusable software and COTS presented in
this project functions as a guide for how to accomplish new
software components and COTS in a complex system (Anderso,
Smith and Ward, 2007). The purpose of this project is help in
identifying the techniques and collaborative processes in
handling the new software components, and to address the risks
and other issues. Some of the actions that must be taken to
address the risk and issues include identification of the
components that can be shared across the software system and
encourage their use (Anderso, Smith and Ward, 2007).
Project Scope
describes its relationship to other program plans (Anderso,
Smith and Ward, 2007). The anticipated deliveries include: to
eliminate the baseless production of similar but different

software components which are reusable across the organization
and support the quantity discounts if possible. Secondly is to
describe strategies for the program and approaches to managing
and developing software components and COTS, which provide
an origin for supporting roles and possesses (Anderso, Smith
and Ward, 2007). Thirdly is to provide a summary of roles of
the program that are affected by development plan and includes
an overview of the operation that supports the software plan
strategies. Additionally, to ensure software development plan is
implemented by describing the programs processes. Finally, to
describe the activities that exceeds the development of the
systems and employs reusable software components. However,
the project is not going to cover how the system will be
maintained and the procedure of installation, therefore it is
upon the company to recruit experts.
Project Assumptions
The initial conditions of the project include the schedule for
working hours occurs between9:00am-4:00 pm. At least six
staffs will be working at 20% dedicated time. Failover setups
are based on the timeframe of 5:30 am to 6:30 pm. The
availability of staff vendor and partner needed. The final
conditions are the staff who will be dedicated will remain in
their current roles. The choice of the research will not be
modified. The staffs who are dedicated will cross-train one
another. New hardware is functional. The testing of the database
will utilize mercury load runner and will require a professional
team. Finally, there is availability of facilities staffs and ESD
Networking
Summary milestone schedule
November 1, 2015 – Project Plan Complete and Approved
December 31, 2015 –Design Completed
February 31, 2016 – Coding Completed

April 30, 2016 – Testing Completed
June 31, 2016 – Beta Testing Completed
July 30, 2016 – Execution Completed
Oct 15, 2016 - One Performance Cycle Complete and Project
Completion
Project Budget
Expenses
Total cost (p.m.)$
Staffs
2000
Consultancy
2490
Guest speakers
1432
lodging
500
Train
1000
Per Diem
436
Material
234
catering
655
Total
8747
References
https://resources.sei.cmu.edu/asset_files/TechnicalReport/2007_

005_001_14882.pdf
http://www.projectmanagementwatch.co.uk/wp-
content/uploads/2015/03/project-budget-template-excel.jpg
You need to submit the term project you had selected in Module
1. The purpose of the project is to give you an opportunity to
apply what you have learned in the course.
A project management plan is a document that is used to guide
and control a project. It includes a project overview, structure,
processes, requirements, risk, schedule, deliverables and
budget.
Use the headings provided in textbook Chapter 4, Section
Project Management Plan Contents (Pages 161-164) to create a
project management plan for the term project you have chosen.
Include the Project Charter and Project Scope Statement in the
Appendix.
Your work should be submitted in a Word document, 8-12 pages
in length (including the appendices), typed in double-space, in
10- or 12-point Arial or Times New Roman font. The page
margins on the top, bottom, left side, and right side should be 1
inch each. You should use the APA guidelines for writing and
citations

Running head M7A1 - PROJECT MANAGEMENT PLAN1M7A1 - PROJECT.docx

More Related Content

Similar to Running head M7A1 - PROJECT MANAGEMENT PLAN1M7A1 - PROJECT.docx (20)

More from joellemurphey (20)

Recently uploaded (20)

Running head M7A1 - PROJECT MANAGEMENT PLAN1M7A1 - PROJECT.docx