Project Name Project Plan Publish Date Project Plan

<Project Name> Project Plan <Publish Date>

Project Plan Components • Project Overview – Description and Strategy • Business Case Summary • Key Deliverables and Scope • Critical Success Factors / Measures of Success • Timelines and Milestones • Project Organization • Resource Requirements • Communications • Key Considerations • Key Risks • Management Approaches

Project Overview Project Background – Historical information that relates to this project <Describe the research that has been completed during the proposal of this project. The business background should provide an understanding of the events leading up to the project. It provides a high level description of the history behind the project. >

Project Overview Objectives of the Project Part One <All projects should support OBR and tie to company strategic goals. The objectives should be SMART>

Project Overview Strategic Alignment Part Two Organizational Drivers Organizational Goals Group Goals Program Management Goals

Business Case Summary Executive Summary Objective – Opportunity to state your case and gain interest <State what business need the project is solving>

Key Deliverables – Produced by the team to ensure success <List the specific deliverables that will be produced by the project team. A deliverable is any outcome that must be produced to complete the project or part of a project. List as many as needed with the most important one first> Deliverables <Project Management Guide> <SD Handbook> <Web Based Methodology> <SD Template>

Critical Success Factors / Measures of Success Critical Success Factors – Used to determine if the project is successful • <Identify the critical success factors> • <Critical Success Factor>

Project Timeline <Use print screen to paste copy of schedule here>

Project Organization Chart <Paste here>

Resource Plan Area Budgeted Hours Business Team <Number> Consulting <Number> Core Team <Number> Total Hours <Number>

Key Considerations Assumptions/Constraints – Items believed to be true for the project and project limits Assumptions • <Assumption> Constraints • <Constraint> Related Projects/Affected Systems • <RP/AS>

Key Risks Risk Assessment – Factors that may have a negative impact on the project • <Identify the key risks> • <Key Risk>

Management Approaches • Integration Management • Quality Management • Human Resource – Issue / Change Control Management / Project Information • Communication • Scope Management • Time Management* • Risk Management* • Cost Management* • Procurement Management *required

Integration Management Approach Issue Management Key Steps Tools Role Frequency Identify Issues Issue log Entire team As they arise Assess Impact Issue log Project Manager During identification Prioritize the issue Issue log Project Manager During assessment Resolve the issue Issue log Project Manager As resolution occurs Review with team Project Status Report Project Manager Weekly or biweekly Track issues Issue log Project Manager Throughout the project

Integration Management Approach Change Management Key Steps Tools Role Frequency Identify Change Request for Change Form Entire team As they arise Assess Impact Request for Change Form Project Manager During identification Recommend Action Request for Change Form Project Manager During assessment Authorize Change – Request for based on change Change Form control procedures and thresholds Project Manager/ Project Sponsor As approval resolution occurs Review with team Project Status Report Project Manager Weekly or biweekly/ As needed Track issues Change log Project Manager Throughout the project

Integration Management Approach Project Information Management Key Steps Tools Determine the naming structure for the project files and folders Role Frequency Project Manager Start of the Planning Process and updated storage areas weekly or biweekly Set version control Project Manager Start of the Planning Process Assign information owners Project Manager Start of the Planning Process Manage information flow Project Manager Update the team weekly or as needed Decide space for the project repository and how often information will be uploaded and updated Company specific standards, procedures, and policies

Scope Management Approach Key Steps Define and plan scope Tools Project Initiation Document Baseline Scope Role Frequency Project Manager/ Program Manager During Initiating Process Project Manager After the Planning Approval Checkpoint Update scope as needed – based upon change control procedures and thresholds Request for Change form/ Change Log Project Manager/ Project Sponsor As needed and approved Baseline and revise Project Schedule/ Project Budget Project Manager As needed and approved Review with team Project Status Report Project Manager Weekly/ biweekly

Time Management Approach Key Steps Tools Role Frequency Create schedule Microsoft Project Manager During Initiating Process Baseline schedule Triple constraint rule – Time, Cost, Schedule Project Manager After the Planning Approval Checkpoint Track hours of work Time Tracking Tool Team Weekly Members Track progress Microsoft Project Manager Weekly Change schedule – based upon change control procedures Request for Change/ Change Log Project Manager As needed and approved Re-baseline as approved Project Budget/ Project Schedule Project Manager As needed and approved

Cost Management Approach Key Steps Create budget Tools Budget template Baseline budget Role Frequency Project Manager/ Program Manager During Initiating Process Project Manager After the Planning Approval Checkpoint Track time Tracking Tool Project Manager Weekly Monitor budget (Actual vs. Budget) Budget Template Project Manager Weekly Change budget Request for Change/ Change Log Project Manager As needed and approved Review budget Executive Status Report/ Project Status Report Project Manager As needed and approved

Quality Management Approach Key Steps Tools Role Frequency Set quality standards Quality Assurance Template/ CM Guideline Project Manager During Planning Process Track defects Defect Tracking Log Delegated Team Member Weekly or monthly Review quality standards with team SRS/ Project Status Reports Project Manager Biweekly

Human Resource Management Approach Key Steps Tools Role Frequency On Board Team Kick Off Meeting/ Project Plan Project Manager When assembled Define team roles Roles and Responsibility Matrix Project Manager As staff is identified Allocate/ direct and review project work Project Schedule Project Manager Weekly or Biweekly Review team Project Status members and provide Reports feedback Project Manager Biweekly, monthly or at the end of phases

Communication Management Approach Key Steps Tools Role Frequency Organize team roles Organization Chart/ Roles and Responsibility Matrix Project Manager During Planning process and as new members are added Create communication plan Communication Matrix Project Manager During Planning process Report project progress Team Member Status Report Team Members Weekly or Biweekly Review progress with the team Meeting Agenda/ Meeting Notes/ Project Status Report Project Manager Weekly or Biweekly Review progress with senior management Executive Status Report Project Manager Monthly

Risk Management Approach Key Steps Tools Role Frequency Identify Risks Risk Log All team members Entire project Analyze the impact and plan response Risk Log Project Manager As identified Risks with level of High need detailed analysis Detailed Risk Response Project Manager As analyzed Review risk with team Project Status Report Project Manager Weekly or Biweekly Review risks with senior management Executive Status Report Project Manager Monthly

Procurement Management Approach Key Steps Tools Role Frequency Review work to be delivered Vendor Statement Project of Work Manager and Vendor Prior to vendor start date Manage vendor communications Project Status Reports Weekly or biweekly Project Manager

Attachments to Project Plan • Project Initiation • Additional Document Management Plans • Business Case • Supporting Lifecycle Documents • Communication Matrix – Requirements or • Roles and Software Responsibility Matrix Requirements Specifications • Schedule – Deployment Plan • Vendor’s Statement of Work