PM586 UOP Wk 3 Establishing a New Branch for Free Software Foundation Paper Develop the project budget for your proposal, and include a copy of it in your

PM586 UOP Wk 3 Establishing a New Branch for Free Software Foundation Paper Develop the project budget for your proposal, and include a copy of it in your project plan.Update the Budget portion of your Template with the following including an opening paragraph (NOTE: you are updating the budget table I Provided you in the template):· Identify available resources (consider subcontractors).· Create a labor budget.· Create a capital budget.· Align the schedule and scope to the labor and capital budget.Develop the risk management plan for your project proposal Develop a Risk Register which includes the currently identified risks for your project, what the priority of the risk is and if it is an internal or external risk. (You can Google search a format to use)Define an appropriate contingency plan and budget for the risks identified. Updated in Budget Table provided in template. Submit your Project Management Plan Template Word document. (Template I provided in Week 1 with all other sections intact)

Use this space to build your submission.
You can add text, images, and files.

Add Content

Details & Information
Due date10/1/19, 1:59 AM (CDT) NOTE: As you complete each section for Week 1, 2, 3, and 4 remove the
Green and black text in the template (unless otherwise noted) as you update
each section with your own thoughts on how you will manage the project you
are proposing. You MUST keep all other sections intact each week (see
Grading Rubric). Using sections verbatim from the Template is considered
Plagiarism and the template is just an Example of what should be in each
section. Each section should be updated with your OWN work no direct
quotes.
PROJECT MANAGEMENT PLAN
Establishing a New Branch for the Free Software Foundation
FREE SOFTWARE FOUNDATION
51 FRANKLIN STREET, FIFTH FLOOR
BOSTON, MASSACHUSETTS 02110
SEPTEMBER 17, 2019
Project Management Plan Template
www.ProjectManagementDocs.com
TABLE OF CONTENTS
INTRODUCTION ……………………………………………………………………………………………………………….. 2
PROJECT MANAGEMENT APPROACH AND PHASES ………………………………………………………………… 2
PROJECT SCOPE AND REQUIREMENTS …………………………………………………………………………………. 2
SCHEDULE AND WORK BREAKDOWN STRUCTURE ………………………………………………………………… 3
CHANGE MANAGEMENT PLAN …………………………………………………………………………………………… 3
COMMUNICATIONS MANAGEMENT PLAN …………………………………………………………………………….. 4
WORK MANAGEMENT PLAN ………………………………………………………………………………………………. 6
PROJECT MONITORING STRATEGIES …………………………………………………………………………………… 7
QUALITY MANAGEMENT PLAN ………………………………………………………………………………………….. 7
RISK MANAGEMENT PLAN ………………………………………………………………………………………………… 8
STAFFING MANAGEMENT PLAN …………………………………………………………………………………………. 9
BUDGET ……………………………………………………………………………………………………………………….. 10
SPONSOR ACCEPTANCE …………………………………………………………………………………………………… 11
REFERENCES …………………………………………………………………………………………………………………. 12
1
Project Management Plan Template
www.ProjectManagementDocs.com
INTRODUCTION
Include the following from Week 1 – This section is NOT written in bullets in your document
•
The organization’s name
•
The purpose for this organization’s existence
•
Why this organization is of interest to you
•
A detailed and clear description of the project and its relationship to the organization’s
business objectives
PROJECT MANAGEMENT APPROACH AND PHASES
Week 2 update. 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.
This section also includes what project management Phases you will be using throughout the
execution of your project.
The Project Manager, Joe Green, has the overall authority and responsibility for managing and
executing this project according to this Project Plan and its Subsidiary Management Plans. The
project team will consist of personnel from the coding group, quality control/assurance group,
technical writing group, and testing group. The project manager will work with all resources to
perform project planning. All project and subsidiary management plans will be reviewed and
approved by the project sponsor. All funding decisions will also be made by the project sponsor.
Any delegation of approval authority to the project manager should be done in writing and be
signed by both the project sponsor and project manager.
The project team will be a matrix in that team members from each organization continue to
report to their organizational management throughout the duration of the project. The project
manager is responsible for communicating with organizational managers on the progress and
performance of each project resource. The project phases will be planning, requirements
gathering, design, development, testing, and Implementation.
PROJECT SCOPE AND REQUIREMENTS
Week 2 update. State the scope and requirements 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
2
Project Management Plan Template
www.ProjectManagementDocs.com
product. This will help to clarify what is included in the project and help to avoid any confusion
from project team members and stakeholders.
The scope of TSI’s SmartVoice project includes the planning, design, development, testing, and
transition of the SmartVoice voice recognition software package. This software will meet or
exceed organizational software standards and additional requirements established in the project
charter. The scope of this project also includes completion of all documentation, manuals, and
training aids to be used in conjunction with the software. Project completion will occur when the
software and documentation package has been successfully executed and transitioned to TSI’s
manufacturing group for production.
All SmartVoice project work will be performed internally and no portion of this project will be
outsourced. The scope of this project does not include any changes in requirements to standard
operating systems to run the software, software updates or revisions.
SCHEDULE AND WORK BREAKDOWN STRUCTURE
Week 2 update. This section should include your schedule either done in MS Project and a
screen shot inserted or in Excel with screen shots inserted here along with an opening summary
paragraph. It should include activities, duration, WBS, and resources needed to complete your
project
CHANGE MANAGEMENT PLAN
Week 4 update. This section should describe your change control process. Ideally, this process
will be some type of organizational standard which is repeatable and done on most or all projects
when a change is necessary. Changes to any project must be carefully considered and the impact
of the change must be clear in order to make any type of approval decisions. Many organizations
have change control boards (CCBs) which review proposed changes and either approve or deny
them. This is an effective way to provide oversight and ensure adequate feedback and review of
the change is obtained. This section should also identify who has approval authority for changes
to the project, who submits the changes, how they are tracked and monitored.
For complex or large projects the Change Management Plan may be included as an appendix to
the Project Management Plan or as a separate, stand-alone document. We have a detailed
Change Management Plan template available on our website.
The following steps comprise TSI’s organization change control process for all projects and will
be utilized on the SmartVoice project:
Step #1: Identify the need for a change (Any Stakeholder)
Requestor will submit a completed TSI change request form to the project manager
Step #2: Log change in the change request register (Project Manager)
The project manager will maintain a log of all change requests for the duration of the
project
3
Project Management Plan Template
www.ProjectManagementDocs.com
Step #3: Conduct an evaluation of the change (Project Manager, Project Team, Requestor)
The project manager will conduct an evaluation of the impact of the change to cost, risk,
schedule, and scope
Step #4: Submit change request to Change Control Board (CCB) (Project Manager)
The project manager will submit the change request and analysis to the CCB for review
Step #5: Change Control Board decision (CCB)
The CCB will discuss the proposed change and decide whether or not it will be approved
based on all submitted information
Step #6: Implement change (Project Manager)
If a change is approved by the CCB, the project manager will update and re-baseline
project documentation as necessary as well as ensure any changes are communicated to
the team and stakeholders
Any team member or stakeholder may submit a change request for the SmartVoice Project. The
SmartVoice Project Sponsor will chair the CCB and any changes to project scope, cost, or
schedule must meet his approval. All change requests will be logged in the change control
register by the Project Manager and tracked through to completion whether approved or not.
COMMUNICATIONS MANAGEMENT PLAN
Week 4 update. 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.
This Communications Management Plan sets the communications framework for this project. It
will serve as a guide for communications throughout the life of the project and will be updated as
communication requirements change. This plan identifies and defines the roles of SmartVoice
project team members as they pertain to communications. It also includes a communications
matrix which maps the communication requirements of this project, and communication conduct
for meetings and other forms of communication. A project team directory is also included to
provide contact information for all stakeholders directly involved in the project.
4
Project Management Plan Template
www.ProjectManagementDocs.com
The Project Manager will take the lead role in ensuring effective communications on this project.
The communications requirements are documented in the Communications Matrix below. The
Communications Matrix will be used as the guide for what information to communicate, who is
to do the communicating, when to communicate it, and to whom to communicate.
Communicatio
n Type
Weekly Status
Report
Weekly Project
Team Meeting
Project
Monthly
Review (PMR)
Project Gate
Reviews
Technical
Design Review
Description
Email
summary of
project
status
Meeting to
review
action
register and
status
Present
metrics and
status to
team and
sponsor
Present
closeout of
project
phases and
kickoff next
phase
Review of
any
technical
designs or
work
associated
with the
project
Frequenc
y
Format
Weekly
Email
Weekly
In
Person
Monthly
Participants/
Distribution
Project
Sponsor,
Team and
Stakeholders
Deliverable Owner
Status
Report
Project
Manager
Project Team
Updated
Action
Register
Project
Manager
In
Person
Project
Sponsor,
Team, and
Stakeholders
Status and
Metric
Presentatio
n
Project
Manager
As
Needed
In
Person
Project
Sponsor,
Team and
Stakeholders
Phase
completion
report and
phase
kickoff
Project
Manager
As
Needed
In
Person
Project Team
Technical
Design
Package
Project
Manager
Project team directory for all communications is: This table can be used but must be
updated with your information for your project.
Name
Title
E mail
Office Phone
Cell Phone
John Davis
Project Sponsor
j.davis@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
5
Project Management Plan Template
www.ProjectManagementDocs.com
Joe Green
Herb Walker
Jason Black
Mary White
Ron Smith
Tom Sunday
Karen Brown
Project Manager
Senior
Programmer
Programmer
Sr. Quality
Specialist
Quality
Specialist
Technical Writer
Testing
Specialist
j.green@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
h.walker@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
j.black@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
m.white@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
r.smith@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
t.sunday@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
k.brown@tsi.com
xxx-xxx-xxxx
xxx-xxx-xxxx
Communications Conduct:
Meetings:
The Project Manager will distribute a meeting agenda at least 2 days prior to any scheduled
meeting and all participants are expected to review the agenda prior to the meeting. During all
project meetings the timekeeper will ensure that the group adheres to the times stated in the
agenda and the recorder will take all notes for distribution to the team upon completion of the
meeting. It is imperative that all participants arrive to each meeting on time and all cell phones
and blackberries should be turned off or set to vibrate mode to minimize distractions. Meeting
minutes will be distributed no later than 24 hours after each meeting is completed.
Email:
All email pertaining to the SmartVoice Project should be professional, free of errors, and provide
brief communication. Email should be distributed to the correct project participants in
accordance with the communication matrix above based on its content. All attachments should
be in one of the organization’s standard software suite programs and adhere to established
company formats. If the email is to bring an issue forward then it should discuss what the issue
is, provide a brief background on the issue, and provide a recommendation to correct the issue.
The Project Manager should be included on any email pertaining to the SmartVoice Project.
Informal Communications:
While informal communication is a part of every project and is necessary for successful project
completion, any issues, concerns, or updates that arise from informal discussion between team
members must be communicated to the Project Manager so the appropriate action may be taken.
WORK MANAGEMENT PLAN
Week 4 update. The Work Management plan describes how work, deliverables, documents, and
contingency will be managed on your project. Separate sub-sections needed here for
Deliverables Management (including how you will identify competed deliverables and who will
sign-off, Document Management (including where documents will be stored and who will have
access to them), and Contingency.
6
Project Management Plan Template
www.ProjectManagementDocs.com
PROJECT MONITORING STRATEGIES
Week 4 update. This section provides a general framework for the approach which will be taken
to monitor the project. An overall summary of monitoring the project should be provided along
with a separate sub-section for each of the following and description of how they will be
monitored during your project: Schedule, Budget, Critical Path, Resource levels, Change
requests, and Scope Creep
Schedule
Budget
Critical path
Resource levels
Change requests
Scope creep
QUALITY MANAGEMENT PLAN
Week 4 update. This section discusses how quality management will be used to ensure that the
deliverables for the project meet a formally established standard of acceptance. All project
deliverables should be defined in order to provide a foundation and understanding of the tasks at
hand and what work must be planned. Quality management is the process by which the
organization not only completes the work, but completes the work to an acceptable standard.
Without a thorough Quality Management Plan, work may be completed in a substandard or
unacceptable manner. This section should include quality roles and responsibilities, quality
control, quality assurance, and quality monitoring.
For larger or more complex projects, the Quality Management Plan may be included as an
appendix or separate document. A detailed Quality Management Plan is available for use on our
website.
All members of the SmartVoice project team will play a role in quality management. It is
imperative that the team ensures that work is completed at an adequate level of quality from
individual work packages to the final project deliverable. The following are the quality roles and
responsibilities for the SmartVoice Project:
The Project Sponsor is responsible for approving all quality standards for the SmartVoice
Project. The Project Sponsor will review all project tasks and deliverables to ensure compliance
with established and approved quality standards. Additionally, the Project Sponsor will sign off
on the final acceptance of the project deliverable.
The Project Manager is responsible for quality management throughout the duration of the
project. The Project Manager is responsible for implementing the Quality Management Plan
7
Project Management Plan Template
www.ProjectManagementDocs.com
and ensuring all tasks, processes, and documentation are compliant with the plan. The Project
Manager will work with the project’s quality specialists to establish acceptable quality
standards. The Project Manager is also responsible for communicating and tracking all quality
standards to the project team and stakeholders.
The Quality Specialists are responsible for working with the Project Manager to develop and
implement the Quality Management Plan. Quality Specialists will recommend tools and
methodologies for tracking quality and standards to establish acceptable quality levels. The
Quality Specialists will create and maintain Quality Control and Assurance Logs throughout the
project.
The remaining member of the project team, as well as the stakeholders will be responsible for
assisting the Project Manager and Quality Specialists in the establishment of acceptable quality
standards. They will also work to ensure that all quality standards are met and communicate any
concerns regarding quality to the Project Manager.
Quality control for the SmartVoice Project will utilize tools and methodologies for ensuring that
all project deliverables comply with approved quality standards. To meet deliverable
requirements and expectations, we must implement a formal process in which quality standards
are measured and accepted. The Project Manager will ensure all quality standards and quality
control activities are met throughout the project. The Quality Specialists will assist the Project
Manager in verifying that all quality standards are met for each deliverable. If any changes are
proposed and approved by the Project Sponsor and CCB, the Project Manager is responsible for
communicating the changes to the project team and updating all project plans and
documentation.
Quality assurance for the SmartVoice Project will ensure that all processes used in the
completion of the project meet acceptable quality standards. These process standards are in
place to maximize project efficiency and minimize waste. For each process used throughout the
project, the Project Manager will track and measure quality against the approved standards with
the assistance of the Quality Specialists and ensure all quality standards are met. If any changes
are…
Purchase answer to see full
attachment