Expert answer:Find the template and fill it .

Answer & Explanation:Please refer to the PM3.11.Planning Format pdf document . PM3.11_Planning_Plan_Format.pdf So to recap, I need help with the:1-Risk Register2-Staff Managementfind a better template for the staff management plan and risk register or make one,and fill it and explain what you did exactly .risk_register_Card_Reader_Project.xlsx WBS_Card_ReaderProject.JPG thank you .
pm3.11_planning_plan_format.pdf

risk_register_card_reader_project.xlsx

wbs_card_readerproject.jpg

Unformatted Attachment Preview

Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
The Project Plan
Template
The project plan forms the basis for all management efforts associated with the
project. A project plan template is included in this document.
The information contained in this plan is required for IT projects in varying
degrees. The actual plan items required are defined specifically in project
management policies. The exact format of the information may vary from the
template; however, the basic information is required as defined.
The
Project
Plan
This plan template emphasizes documenting only the pertinent information
associated with the plan. The blank template for the project plan is provided in
Appendix B: Templates & Sample Forms.
The information associated with the plan evolves as the project moves through
its various stages and is updated as new information is determined about the
project.
The plan does not require verbose textual content filled with boilerplate
material. Information associated with detailed procedures for executing such
processes as technical development, configuration management, and quality
assurance should be documented in the state organization’s procedures. For
example, the configuration management information contained in the plan
might reference a procedures document that defines the specific activities and
responsibility for each configuration item. The project plan only summarizes
who is responsible for the configuration management activities, what is under
configuration control, and where the repository will reside.
The project plan documents the project planning process and consists of the
following basic tasks:
•
Defining the sequence of tasks to be performed.
•
Identifying all deliverables associated with the project.
•
Defining the dependency relationship between tasks.
•
Estimating the resources required to perform each task.
•
Scheduling all tasks to be performed.
•
Defining the budget for performing the tasks.
•
Defining the organization executing the project.
•
Identifying the known project risks.
•
Defining the process ensuring quality of the project product.
•
Defining the process for configuration management.
•
Defining the process specifying and controlling requirements.
The plan documents and defines the objectives of the project, the approach to be
taken, and the commitment being assumed. The project plan evolves through
Project Management Methodology
PM Planning
Project Plan Format
Page 1
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
the early stages and, at project start-up time, contains the detail required to
successfully execute the project. Once project execution begins, the plan should
be reviewed, baselined, and updated on a regular basis.
It is important that project plans are approved prior to beginning a project.
These approvals should be easily located at the beginning of the plan to
emphasize support for the project plan. In the template format, approval
signatures are included on the cover of the plan, as shown below.
Plan Approval
Project Management Plan Approval Signatures Form
(Page one of the sample)
PROJECT MANAGEMENT PLAN
Project Name: Document Handling System
August 1, 1996
Date:_______________________________
1.0
Plan Release #:_______________________
John Smith
Project Manager: _____________________
Approvals:
John Smith
Betty White
Project Manager
Prime Contractor Manager – If applicable
Tom Snow
Steve Brown
State Organization Mangement
User Management
Faye McNeill
Peter Chan
Oversight Manager (if applicable)
DOIT
Gene Tim
Tina Black (DGS)
Department of Finance)
Other:
Project Management Methodology
PM Planning
Project Plan Format
Page 2
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
Project Summary
Following the approvals page, there should be a project summary and charter
information that defines:
•
The estimated value of the project.
•
The project deliverables.
•
The duration of the effort.
•
The purpose of the project.
•
The goals, acceptance, and completion criteria.
•
Assumptions made affecting cost and/or schedule.
•
Major dependencies/constraints.
The Project Summary, begun at project initiation, is maintained over the course
of the project. The first page includes areas that need to be filled in and then
updated with each new release of the plan. These include:
•
Project name and start date.
•
State organization, name, and submitted by.
•
Prime Contractor (if applicable) and date awarded.
•
Current stage of the project.
•
Project status in terms of schedule and budget.
•
Budget summary.
Page 2 of the Project Summary includes points of contact and prime contractor
information.
The following two pages show a completed sample project summary from the
template.
Project Management Methodology
PM Planning
Project Plan Format
Page 3
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
1. Project Summary (Sample)
Information in the project summary areas was started during the project concept phase and should be included here
Project Name:
Document Handling System
Start Date:
August 15, 1996
State Organization:
EDD
Submitted By:
John Smith
Prime Contractor:
Vision Quest
Date Awarded:
June 30, 1996
Current Stage of
Project:
Development Life Cycle (Design, Development, Integration, Testing or Implementation)
Project
is On
Schedule:
Yes:
X
X
No:
Details are on page 6
Project is
within
Budget:
Yes:
No: X
Comments:
Additional funds were needed to add
more hardware for statewide rollout
Please answer the following questions by marking “Yes” or “No” and provide a brief response as
appropriate
Is this an updated Project Plan? If so, reason for update: Included
additional activities for
Project Management Methodology
PM Planning
No
X
statewide rollout
Budget for project by fiscal year and is project funded? If so, for what amount(s) and periods(s):
Budget Amount: 1.2 m
Year: FY 96
Budget Amount: .8
Year: FY 97
Budget Amount:
Year:
Total Amount: 2.0 m
Yes
Funded?
Funded?
Funded?
X
X
Project Plan Format
Page 4
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
Project Summary – Continued
Points of Contact
This should be the list of individuals that will be involved with the project during the execution phase.
Position
Project Manager
Senior Management Sponsor
Senior Technical Sponsor
Procurement Contact
Customers:
Unemployment
Audit
Compliance
Name / Organization
John Smith EDD
Joe Done EDD
Mary Lane EDD
Tina Black DGS
Phone
916-692-0962
916-752-1666
916-359-0993
916-425-1254
E-Mail
JSmith@EDD.gov
JDone@EDD.gov
MLane@EDD.gov
TBlack@DGS.gov
Bill Nick
Anne Wright
Lance Gonlin
916-694-3442
916-358-6996
916-536-8888
BNick@EDD.gov
AWright@EDD.gov
LGonlin@DGS.gov
Other Stakeholders (Top 3):
Same as above
Prime Contractor Information
Company:
Phone
E-Mail
Project Manager
Betty White
415-664-3229
BWhite@VQuest.com
Senior Management Sponsor
Ned Jack
415-664-3994
NJack@VQuest.com
Senior Technical Sponsor
Bob Bowman
415-664-6421
BBowman@VQuest.com
Position
Project Management Methodology
Name
PM Planning
Project Plan Format
Page 5
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
Project Charter
The project charter follows the project summary information. Like the project
summary, the project charter information was developed during the project
conception and definition phase and includes a business problem, statement of
work, objective, success factors, project dependencies, and constraints. In the
plan template, this information is contained on two pages or in the following
two figures. A sample of the completed information from the template is shown
below.
2. Project Charter(Sample)
B.
Project Charter:
Business Problem.
All projects start with a business problem/issue to solve.
Sample
The lack of a statewide automated planning system for scheduling transportation road repair maintenance resources has
resulted in road closures, duplicated capital expenditures, and increased staff overtime costs.
Statement of Work (Goal).
The statement should be short and to the point. It should not contain language or terminology that might not be understood.
Sample
Design and prototype an automated, dynamic planning system by Q4, 1997, based on an SQL database and GUI front end.
Based on the prototype, pilot the system and complete full implementation by Q4, 1998.
Project Objectives:
Provide a brief, concise list of what the project is to accomplish.
The project objectives are a detailed version of the statement of work. Taken with the statement of work, the objectives
define the boundaries (scope) of the project. The objective statement can also be seen as a decomposition of the statement
of work into a set of necessary and sufficient objective statements, including:
Outcome – Be specific in targeting an objective
Measurement- Establish a measurable indicator(s) of the progress
Ownership – Make the object assignable to a person for completion
Timeframe – State what can realistically be done with available resources
Sample
1.
2.
3.
4.
5.
6.
7.
Define the planning requirements for the system by Q2, 1997
Define user needs in terms of inputs and outputs by Q2, 1997
Conduct user and stakeholder meetings during Q1 and Q2, 1997
Develop the prototype and test, with a completion date of Q4, 1997
Conduct the pilot of system with completion by Q2, 1998, with the pilot lasting at least three months
Complete system acceptance and user documentation by Q3, 1998
Complete system installation at all locations by Q4, 1998
Project Management Methodology
PM Planning
Project Plan Format
Page 6
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
Managing a project requires the balancing of three factors: resource, schedule,
and scope. These three factors are interrelated, i.e., a change in one of them
causes the others to change as well. The project trade off matrix shows the
relative importance of each factor:
Project Trade Off
Matrix and Status
Summary
•
constrained means the factor cannot be changed
•
accepted means the factor is somewhat flexible to the project
circumstance
•
improved means that the factor can be adjusted.
Also included on this page of the template is a matrix for project status. The
matrix reflects whether the technical, schedule, and cost estimates for each task
are behind, on schedule, or ahead of schedule. Comments are added for any
deviation from the original estimate. For each project, the unique teams or
phase should be filled in the appropriate category.
3. Project Tradeoff Matrix and Status Summary
Schedule
Scope
Resources
CONSTRAINED
ACCEPTED
IMPROVED
Identify variable to be CONSTRAINED, IMPROVED, ACCEPTED
+/- Status
Team/Phase
Technical
Schedule
Cost
Comment
Req
On
Ahead
On
Dev Team 1
On
Ahead
On
Dev Team 2
On
On
On
Testing
On
On
On
Completed this phase ahead of schedule,
on budget
Completed this phase ahead of schedule,
on budget
Completed this phase ahead of schedule,
on budget
Cannot be closed until installation is
complete
Behind
Behind
On
Installation
Project Management Methodology
Additional pieces of hardware were required
to complete statewide rollout causing impact
to technical, schedule & cost
PM Planning
Project Plan Format
Page 7
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
The project plan should include a description of the organization that defines
the persons responsible for the following types of functions: project manager,
development manager, quality assurance, and configuration management. A
project manager is required for every project.
Project Organization
Many plans may also include a narrative of key project member responsibilities.
This would include the person’s name, project position, and key
responsibilities.
Small projects will require less organizational definition than larger projects,
but responsibilities should always be defined.
A sample project organization chart is shown in the following figure. Most
times this information is graphically presented.
4. Project Organization (Sample)
XX Technology
Project
Project Manager
PM Level 4
Subject Experts
Project Admin
PM Assist.
Software Task
Manager
PM – Level 3
Database
Manager
PM – Level 2
Desktop
Systems
Manager
PM – Level 1
Technical Lead
Project Resource
Task Manager
Hardware / Comm
Task Manager
Project Services
Task Manager
PM – Level 2
PM Level 3
PM – Level 3
Budgeting
Manager
PM – Level 1
Operating
Systems
Project Mgr
PM – Level 2
Project Management Methodology
Scheduling
Manager
Level 1
Project
Quality
Manager
Level 1
WAN
Manager
PM – Level 2
Training
Manager
PM – Level 2
LAN
Manager
PM – Level 2
External I&V
Contractor
Staff
Documentation
Manager
PM – Level 2
Integration
Manager
PM – Level 2
PM Planning
Project Plan Format
Page 8
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
Activity sequencing involves dividing the project into smaller, more
manageable components (activities) and then specifying the order of
completion. The following figure shows: 1) activities organized in outline form,
and 2) activities in graph form.
Activity List
5. Activity List (Sample Work Breakdown Structure)
Provide an activity list (work breakdown structure) that describes each task required by the project, with a reference to the statement of work. For large projects,
work packages might be included that describe in detail how specific tasks will be completed by specific project teams. These work packages describe required
schedule, identify requirements to be completed and describe specific work to be performed
Activity #
Activity
Name
Activity Name
Description
# of
Days
Start
Date
1
Design
System Architecture
30
9/1/96
2
Develop
System Development
40
10/1/96
2.1
Code
Code Sub-routine
20
2.2
Integrate
Integrate Sub-routine
20
3
Testing
Testing System
30
11/10/96
4
Installation
State Rollout
35
12/15/96
4.1
Pilot
Pilot Installation
15
12/15/96
4.2
Statewide
Statewide Installation
20
01/15/96
5
Support
Provides User Support
60
12/30/96
4.1FS
6
Training
Provide User Training
20
12/15/96
4.1SS
7
Close-Out
Transfer System to
Operations
1
01/30/97
4.2FS + 5 day
lag
Dependency
Milestone
Detailed Design
IFS
Software Code
Completed Accept.
test of doc
4.1FS + 5 day
lag
Installation
Certificate
Training
Certificate
Legend:
FS = The specific task must finish prior to starting the identified task
SS = Two identified tasks start at the same time, but are not linked to finish at the same time.
FF = Two identified tasks finish a the same time, but are not linked to start at the same time.
Blank = Task has no dependency
Lag = Additional days can be added for reserve to ensure project stays on schedule.
Project Management Methodology
PM Planning
Project Plan Format
Page 9
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
The activity list can also be graphically presented as a work breakdown
structure and included in the project plan. The work breakdown structure,
describes each task required in the project. For large projects, work packages,
with a description showing how specific tasks are to be completed by specific
project teams, may also be included.
Work Breakdown
Structure
These work packages describe required schedules, identify requirements to be
completed and describe specific work to be performed. Refer to Activity
Definition and Sequencing for further information on activity sequencing and
development of a work breakdown structure. A sample graphical work
breakdown structure is shown in the following figure.
Work Breakdown
Schedule (WBS)
Management
Plan Project
Develop Project Plan
Update Project Plan
Track Project
Prepare status report
Collect/analyze
project metrics
Perform Quality
Activities
Prepare QA Plan
Conduct Reviews
Conduct Audits
Perform CM
Prepare CM Plan
Develop Project Library
Manage Change Board
Maintain Configuration
Items
Design
Prepare
Preliminary
Design
Develop Enterprise
Architecture
Prepare Data
Flow Diagrams
Prepare Logical
Data Model
Prepare Detailed
Design
Prepare Physical
Data Model
Prepare Data
Dictionary
Document
Design
Develop Design
Specification
Review Design
Development/
Integration
Develop
Software
Develop Server
Application
Develop User
Interface
Develop XYZ
Interface
Acceptance
Testing
Installation
Maintenance
Plan Acceptance
Test
Develop
Installation Plan
Hardware
Maintenance
Conduct
Acceptance Test
Site Preparation
Software
Maintenance
Develop Test
Report
Install at
Locations
Procure
Hardware
Headquarters
Site One
Procure Server
Procure Workstations
Procure Software
Packages
Procure Databases
Procure User Interface
Building Tool
Procure Operating
System
Perform
Integration
Testing
Convert Data
Develop Conversation
Plan
Develop User
Manual
Transition
Management
Project Management Methodology
PM Planning
Project Plan Format
Page 10
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
Work Product
Identification
The list of project deliverables that includes the date due and the person
responsible for the delivery should be part of the plan. This information is
derived from the project activity list, and is expanded to include the assignment
of the deliverable to a specific author and tracking of delivery of the document.
A sample of the Work Product Identification Template is shown below.
6. Work Product Identification
Provide a list of all deliverables required by the project, the due date and the person responsible for the deliverable.
Deliverable Name
Due Date
Date Delivered
Point of Contact
Design Document
10/1/96
10/15/96
Joe Done
Test Plan
10/1/96
10/15/96
Joe Done
Installation Plan
11/1/96
11/1/96
Terrie Kelly
Source Code
12/1/96
Joe Done
Installation Certificate
1/30/97
Steve Hugh
Training Plan
10/1/96
Training Certificate
1/30/97
Project Management Methodology
10/15/96
Tim Wise
Tim Wise
PM Planning
Project Plan Format
Page 11
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
The project schedule included in the project plan can either be a GANTT or
PERT chart. It should include milestones, task dependencies, task duration,
work product delivery dates, quality milestones (reviews/audits/inspections),
configuration management milestones, and action items (with deadlines and
responsibilities). A sample project schedule is shown below.
Project Schedule
PERT Chart
7. Project Schedule (Sample)
Requirements
Definition (Analysis)
1
8/1/95
9/11/95
Prepare for Analysis
2
8/1/95
8/7/95
Define System
Requirements (Business)
3
ITDE(0.3),ITI
8/8/95
8/14/95
Analyze the Current
System
4
8/8/95
8/14/95
Develop and Evaluate
Alternative Solutions
6
8/15/95
8/21/95
Reaccess Application
Architecture
5
ITDBA(0.3)
8/8/95
8/14/95
Outline Transaction,
Security and Training
7
ITDBA(0.3)
8/15/95
8/21/95
Plan the Next Stage
8
8/22/95
8/28/95
Prepare Material for
Business Management
9
8/29/95
9/4/95
Conduct the Business
Management Review
10
9/5/95
9/11/95
RD Approved by IS Dir,
DMA Dir, Cust Sponsor
11
9/11/95
9/11/95
Approval to Proceed to
Next Stage
12
9/11/95
9/11/95
Project Management Methodology
PM Planning
Project Plan Format
Page 12
Project Management Planning
Project Plan Format
Initial Release
1.0
Date:
January 1997
GANTT Chart
7. Project Schedule (Sample)
Activity Name
April 1996
May 1996
June 1996
July 1996
31 7 19 21 28 5 12 19 26 2 9 16 23 30 7 14
2.0
Design
2.1
Prepare Preliminary D …
Purchase answer to see full
attachment

How it works

1. Paste your instructions in the instructions box. You can also attach an instructions file
2. Select the writer category, deadline, education level and review the instructions 
3. Make a payment for the order to be assignment to a writer
4.  Download the paper after the writer uploads it 

Will the writer plagiarize my essay?

You will get a plagiarism-free paper and you can get an originality report upon request.

Is this service safe?

All the personal information is confidential and we have 100% safe payment methods. We also guarantee good grades