Attached are the files of project idea and project charter template. Project charter need to be filled up on a high level.
project_charter_template.doc

project_idea.docx

Unformatted Attachment Preview

PROJECT MANAGEMENT PLAN

LIST ALL TEAM MEMBER NAMES
DATE
PM600 – PROJECT MANAGEMENT PROCESSES IN ORGANIZATIONS
Project Management Plan Template
TABLE OF CONTENTS
INTRODUCTION ……………………………………………………………………………………………………………….. 2
PROJECT MANAGEMENT APPROACH …………………………………………………………………………………… 2
PROJECT SCOPE……………………………………………………………………………………………………………….. 2
MILESTONE LIST ……………………………………………………………………………………………………………… 2
WORK BREAKDOWN STRUCTURE & YOUR SCHEDULE YOU DEVELOPED ………………………………….. 3
COMMUNICATIONS MANAGEMENT PLAN …………………………………………………………………………….. 3
COST MANAGEMENT PLAN (BUDGET) ………………………………………………………………………………… 4
RISK MANAGEMENT PLAN ………………………………………………………………………………………………… 4
RISK REGISTER ……………………………………………………………………………………………………………….. 4
RESOURCE CALENDAR ……………………………………………………………………………………………………… 4
SPONSOR ACCEPTANCE …………………………………………………………………………………………………….. 4
1
Project Management Plan Template
GROUP PROJECT INSTRUCTIONS
This is to be used to provide the final documents that you have worked on this past session. You
will also need to explain your approach for EACH Section. Please delete these green
instructions in each section and add in your own text based on your project.
INTRODUCTION
The Introduction provides a high level overview of the project and what is included in this
Project Management Plan. This should include a description of the project and the projects
deliverables and benefits. Excessive detail is not necessary in this section as the other sections of
the project plan will include this information. This section should provide a summarized
framework of the project and its purpose. Look back at the Project Charter for information to
include in this section.
PROJECT MANAGEMENT APPROACH
This section is where you outline the overall management approach for the project. This section
should describe, in general terms, the roles and authority of project team members. It should
also include which organizations will provide resources for the project and any resource
constraints or limitations. If there are any decisions which must be made by specific
individuals—for example authorizing additional funding by the project sponsor—this should also
be stated here. It should be written as an Executive Summary for the Project Management Plan.
PROJECT SCOPE
State the scope of the project in this section. The scope statement from the project charter should
be used as a starting point; however, the project plan needs to include a much more detailed
scope than the charter. This detail should include what the project does and does not include.
The more detail included in this section, the better the product. This will help to clarify what is
included in the project and help to avoid any confusion from project team members and
stakeholders.
MILESTONE LIST
Provide a summary list of milestones including dates for each milestone. Include an introductory
paragraph in this section which provides some insight to the major milestones. This section
should also mention or discuss actions taken if any changes to the milestones or delivery dates
are required.
Milestone
Description
Date
2
Project Management Plan Template
WORK BREAKDOWN STRUCTURE & YOUR SCHEDULE YOU DEVELOPED
This section should discuss HOW you developed your WBS Dictionary and Schedule and how
they will be used in managing the project’s scope. The WBS provides the work packages to be
performed for the completion of the project. The WBS Dictionary defines the work packages.
The schedule baseline provides a reference point for managing project progress as it pertains to
schedule and timeline. The schedule baseline and work breakdown structure (WBS) should be
created in Microsoft Project. The WBS can be exported from the MS Project file.
COMMUNICATIONS MANAGEMENT PLAN
The purpose of the Communications Management Plan is to define the communication
requirements for the project and how information will be distributed to ensure project success.
You should give considerable thought to how you want to manage communications on every
project. By having a solid communications management approach you’ll find that many project
management problems can be avoided. In this section, you should provide an overview of your
communications management approach. Generally, the Communications Management Plan
defines the following:
• Communication requirements based on roles
• What information will be communicated
• How the information will be communicated
• When will information be distributed
• Who does the communication
• Who receives the communication
• Communications conduct
For larger and more complex projects, the Communications Management Plan may be included
as an appendix or separate document apart from the Project Management Plan. We have a
detailed Communications Management Plan template available on our website.
EXAMPLE
Communication
Type
Description
Frequency
Format
Participants/
Distribution
Deliverable
Owner
Project team directory for all communications is:
Name
Title
E mail
3
Office Phone
Cell Phone
Project Management Plan Template
COST MANAGEMENT PLAN (BUDGET)
The Cost Management Plan clearly defines how the costs on a project will be managed
throughout the project’s lifecycle. It sets the format and standards by which the project costs are
measured, reported, and controlled. Working within the cost management guidelines is
imperative for all project team members to ensure successful completion of the project. These
guidelines may include which level of the WBS cost accounts will be created in and the
establishment of acceptable variances. The Cost Management Plan:
• Identifies who is responsible for managing costs
• Identifies who has the authority to approve changes to the project or its budget
• How cost performance is quantitatively measured and reported upon
• Report formats, frequency and to whom they are presented
For complex or large projects the Cost Management Plan may be included as an appendix to the
Project Management Plan or as a separate, stand-alone document. We have a detailed Cost
Management Plan template available on our website.
RISK MANAGEMENT PLAN
This section provides a general description for the approach taken to identify and manage the
risks associated with the project. It should be a short paragraph or two summarizing the
approach to risk management on this project.
Since risk management is a science in itself, we have many risk management templates available
on our website. Look for the detailed Risk Management Plan, Risk Register along with
templates for performing a risk assessment meeting.
RISK REGISTER
Provide the updated Risk Register for your group project.
RESOURCE CALENDAR
Include a Resource Calendar as part of your project plan. The resource calendar identifies key
resources needed for the project and the times/durations they’ll be needed. Some resources may
be needed for the entire length of the project while others may only be required for a portion of
the project. This information must be agreed to by the Project Sponsor and Functional Managers
prior to beginning the project.
SPONSOR ACCEPTANCE
Approved by the Project Sponsor:
4
Project Management Plan Template
__________________________________________

5
Date: ___________________
Project Idea
Mobile app for a restaurant:
A mobile app is a software application which runs on mobile instead of a traditional web app which runs
on PCs. A mobile app can be accessed through tablets as well. Below are some of the features we are
going to provide as a part of mobile app.
1)
2)
3)
4)
5)
Location Based services.
Search feature
Social Networking features.
Responsive design.
Allow user feedback.
As we know project management is an important aspect of any project to make it successful. The project
we are going to develop is related to IT industry. Below are some of the duties a project manager needs
to perform.
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
Planning and defining the scope.
Get the approvals from stake holders.
Pool the IT resources required. (Developers, testers, licenses required for the software etc).
Estimating cost and time.
Develop a budget plan.
Make the hard decisions as required.
Have a technical knowledge.
Risk analysis.
Monitor risks and defects in a timely manner.
Create documentation and close out the project.

Purchase answer to see full
attachment