Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
Project Management Plan Revision
Date:April 2004
[Name] ProjectProject Management Plan
Version 0.1
Deliverable Number:
001-XXX-XXX-DEL
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA.
Project Management Plan April 2004 Page ii
Table of Contents
1.0 Executive Summary and Project Overview11.1 Concepts of Operation
11.1.1 Current Environment
11.1.2 Planned Future Environment
11.2 Scope
11.2.1 Project Justification
11.2.2 Project Objectives
11.2.3 Project Deliverables
41.2.4 Scope Management Plan
41.3 Overall Strategy
51.3.1 Project Management
51.3.2 Project Startup
51.3.3 Project Lifecycle
51.3.4 Project Reviews
5
2.0 Project Organization52.1 Roles and Responsibility
5
2.2 Key Organizational Groups6
2.2.1 Identified Stakeholders6
2.2.2 Management Structures6
2.2.3 Project Governance Structure6
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA.
Project Management Plan April 2004 Page iii
2.2.4 Core Team Structure7
2.2.5 Change Control Board (CCB)7
3.0 Project Management73.1 Staffing Plan
7
3.2 Assumptions7
3.3 Constraints8
3.4 Dependencies8
3.5 Risk Management Plan8
3.5.1 PMO Risk Management Approach8
3.5.2 PMO Risk Listing8
3.6 Project Controls9
3.6.1 Project Reporting9
3.6.2 Project Metrics and Measurement9
4.0 REFERENCES:9
5.0 CHANGE HISTORY9
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA.
Project Management Plan April 2004 Page iv
List of Tables
Table 1: Business Objectives.........................................................................................1Table 2: Technical Objectives.........................................................................................2Table 3: Project Management Objectives......................................................................2Table 4: Project Deliverables..........................................................................................4Table 5: Roles and Responsibilities...............................................................................5Table 6: Key Project Stakeholders.................................................................................6Table 7: Governance Members – Deliverable Acceptance..........................................6Table 8: Change Control Board Members.....................................................................7Table 9: Project Staffing Plan.........................................................................................7Table 10: Project Assumptions......................................................................................7Table 11: Project Constraints.........................................................................................8Table 12: Project Dependencies.....................................................................................8Table 13: Project Risk Listing.........................................................................................8Table 14: Metrics..............................................................................................................9Table 15: References.......................................................................................................9
List of Figures
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA.
Project Management Plan April 2004 Page 1
1.0 Executive Summary and Project Overview
[Summary Narrative]
1.1 Concepts of Operation
1.1.1 Current Environment
1.1.2 Planned Future Environment
1.2 Scope
1.2.1 Project Justification
[Narrative]
1.2.2 Project Objectives
[Narrative Summary]
1.2.2.1 Business Objectives
Table 1: Business ObjectivesNumber Description
XXX-BU-001XXX-BU-002XXX-BU-003XXX-BU-004XXX-BU-005XXX-BU-006XXX-BU-007
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 1
Project Management Plan April 2004 Page 2
1.2.2.2 Technical Objectives
Table 2: Technical ObjectivesNumber Description
XXX-TC-001XXX-TC-002XXX-TC-003XXX-TC-004XXX-TC-005XXX-TC-006XXX-TC-007
1.2.2.3 Project Management Objectives
Table 3: Project Management Objectives
Integration Management
Number DescriptionXXX-PM-001 Ensure the project has an approved Project Management Plan.XXX-PM-002 Ensure the project executes in accordance with its approved Project Management Plan.XXX-PM-003 Ensure and overall scope change control process is instituted and followed for the
project for all items in its project management baseline, including the Project Management Plan and its subcomponents.1
Scope Management
Number DescriptionXXX-PM-004 Ensure the project was established formal project requestXXX-PM-005 Ensure the project has identified a project manager for the project.XXX-PM-006 Ensure the project constraints are documented and agreed upon.2
XXX-PM-007 Ensure the project assumptions are documented and agreed upon.XXX-PM-008 Ensure the project dependencies are documented and agree upon.XXX-PM-009 Ensure the project has a clear and complete list of objectives.XXX-PM-010 Ensure the project has a plan for scope management.3
XXX-PM-011 Ensure the project has an accurate Work Breakdown Structure.4
XXX-PM-012 Ensure the project Work Breakdown Structure is decomposed to a sufficient level of detail that allows accurate effort estimation.
Time Management
Number DescriptionXXX-PM-013 Ensure project has an accurate, defined activity sequence (network of dependencies).
1 The change control process in this document section X.2 Continual update of project constraints, assumptions, and dependencies are critical to project success. These are listed beginning in section 3.2 of this document.3 Scope management is executed through the scope change control procedure; however, refer to section 1.2 for an overview of project scope, objectives, and key deliverables.4 The work breakdown structure (WBS) is a component of the integrated master schedule.
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 2
Project Management Plan April 2004 Page 3
Table 3: Project Management ObjectivesXXX-PM-014 Ensure the project has completed resource planning compatible with the schedule and
the dependencies stated in the project plan and activity sequence network.XXX-PM-015 Ensure the project develops a schedule based on its activity sequence, duration
estimates and that the critical path is clearly understood and communicated to all parties.XXX-PM-016 Identify critical path slips of more than 10% of plan via a special management review.XXX-PM-017 Maintain appropriate schedule metrics that provide adequate management visibility into
the status of the schedule.
Cost Management
Number DescriptionXXX-PM-018 Maintain project budget tracking for vendor-supported projects.5
XXX-PM-019 Identify cost overruns on a monthly basis by cost center.XXX-PM-020 Ensure metrics are established for controlling and monitoring the project budget.
Quality Management
Number DescriptionXXX-PM-021 Ensure the project establishes quality measures and metrics that support the
achievement of project business objectives.XXX-PM-022 Ensure lessons learned and process improvements are submitted as a result of the
quality management process.XXX-PM-023 Perform periodic reviews within the PMO to quickly identify and resolve impediments to
software development activitiesXXX-PM-024 Perform periodic reviews of software to ensure that code meets the agreed upon
requirements
Communication Management
Number DescriptionXXX-PM-025 Ensure that a communications management plan exists for the project.XXX-PM-026 Ensure project records are kept up to date and reported in a timely manner.XXX-PM-027 Ensure performance reporting occurs in a manner that reporting occurs based on both
temporal and stage gate trigger set.XXX-PM-028 Ensure that project administrative closure occurs when the project completes.XXX-PM-029 Ensure project archives are created in accordance with the project plan.XXX-PM-030 Ensure lessons learned sessions are conducted, documented, and analyzed for ongoing
process improvement.
Human Resource Management
Number DescriptionXXX-PM-031 Ensure project team roles and responsibilities are clearly delineated.XXX-PM-032 Ensure a staffing management plan is documented for the project.XXX-PM-033 Ensure organizational charts are available for communicating the project structure as
well as its interface to other organizations.XXX-PM-034 Ensure role assignments are filled with qualified staff.XXX-PM-035 Ensure a project team directory exists to communicate project team member information.XXX-PM-036 Ensure project stakeholders are clearly identified and documented in the project plan.XXX-PM-037 Ensure a responsibility assignment matrix is documented for the project and project team
members.XXX-PM-038 Ensure team member goals and objectives are clearly understood by the team members.
5 The budget tracking primarily pertains to invoice and deliverable tracking
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 3
Project Management Plan April 2004 Page 4
Table 3: Project Management ObjectivesXXX-PM-039 Ensure team members receive the proper training to conduct their project
responsibilities.XXX-PM-040 Ensure performance appraisals are completed in a timely manner.
Risk Management
Number DescriptionXXX-PM-041 Identify and resolve issues in a timely manner.XXX-PM-042 Identify risks in a timely manner.XXX-PM-043 Quantify risks as they are identified.XXX-PM-044 Communicate risks in Bi-Weekly Status Reports, monthly PMO program reviews, and at
all formal reviews.XXX-PM-045 Develop risk mitigation strategies for each risk.XXX-PM-046 Proactively resolve risks that are within control of the project.XXX-PM-047 Proactively elevate risks that are outside control of the project.XXX-PM-048 Maintain metrics on risks on the project that provide an accurate account of total project
risk and resolution.
Procurement Management
Number DescriptionXXX-PM-049 Conduct Market Analysis.XXX-PM-050 Conduct Make or Buy Analysis.XXX-PM-051 Develop Request for Proposal (RFP) for contractor support.XXX-PM-052 Develop Criteria for rating RFP's.XXX-PM-053 Determine the appropriate Contract Type to use for a given procurement.XXX-PM-054 Construct Contract for Services or Product.
1.2.3 Project Deliverables
Table 4: Project DeliverablesDeliverable
Number Description ApproverXXX-DL-001XXX-DL-002XXX-DL-003XXX-DL-004XXX-DL-005XXX-DL-006XXX-DL-007XXX-DL-008XXX-DL-009XXX-DL-010
1.2.4 Scope Management Plan
1.2.4.1 Scope Change Control Approach
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 4
Project Management Plan April 2004 Page 5
1.3 Overall Strategy
1.3.1 Project Management
[Narrative and graphics depicting how the project will be managed]
1.3.2 Project Startup
[Approach to project startup]
1.3.3 Project Lifecycle
[Project lifecycle – narrative and graphics documenting how the project will be executed, including key phases and the expected approaches for accomplishing the key objectives of those phases]
1.3.4 Project Reviews
[Narrative describing the key reviews that will take place throughout the project, and when key project baselines will be established]
2.0 Project Organization
2.1 Roles and Responsibility
Table 5: Roles and ResponsibilitiesRole Responsibilities
Project Sponsor
Project Manager
Business Analyst
Technical Lead
PMO
Business Architect
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 5
Project Management Plan April 2004 Page 6
Table 5: Roles and ResponsibilitiesRole Responsibilities
Technical Architect
Vendor/Contractor
Business Users
2.2 Key Organizational Groups
2.2.1 Identified Stakeholders
Table 6: Key Project StakeholdersName Position
2.2.2 Management Structures
2.2.2.1 Management Reporting Structure
[Graphic]
2.2.2.2 Project Management Structure
[Graphic]
2.2.3 Project Governance Structure
[Graphic]
Table 7: Governance Members – Deliverable AcceptanceName Position
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 6
Project Management Plan April 2004 Page 7
2.2.4 Core Team Structure
[Graphic]
2.2.5 Change Control Board (CCB)
2.2.5.1 CCB Overview
[Narrative]
2.2.5.2 CCB Members
Table 8: Change Control Board MembersName Position
3.0 Project Management
3.1 Staffing Plan
Table 9: Project Staffing PlanName Role Status
(Full/Part Time)
3.2 Assumptions
Table 10: Project AssumptionsNo. Assumption
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 7
Project Management Plan April 2004 Page 8
3.3 Constraints
Table 11: Project Constraints
No. Constraints
3.4 Dependencies
Table 12: Project Dependencies
No. Dependencies
3.5 Risk Management Plan
3.5.1 PMO Risk Management Approach
3.5.2 PMO Risk Listing
Table 13: Project Risk ListingRisk
NumberRisk Statement Probability Severity Risk
Score
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 8
Project Management Plan April 2004 Page 9
3.6 Project Controls
3.6.1 Project Reporting
[Narrative on project reporting and communication approaches]
3.6.2 Project Metrics and Measurement
Table 14: MetricsMetric
NumberMetric Description Focus Reported To Frequency
4.0 REFERENCES:
Table 15: ReferencesTitle Code Location
Issues Management Process Document RepositoryRisk Management Process Document RepositoryDeliverable Approval Process Document RepositoryScope Change Control Process Document RepositoryProject Cost Management Document Repository
5.0 CHANGE HISTORY
Version Date Change Description0.1 Initial Draft
2004 NJ UI Modernization Project and Tier Technologies, Inc. All rights reserved. Printed in the USA. 9