The Project Meeting Notes Template is used to Project Meeting Monitor & 2.0 .doc document and communicate notes for all Notes Control project meetings. The Status Report is utilized for communicating Project Status the overall health of the project to the core Monitor & 2.0 .doc team and key project stakeholders to keep Control Report everyone abreast of project progress. The Project Change Request (PCR) is used by Project Change the Project Manager to request a change to Monitor & 2.0 .doc Request the project scope, schedule, costs, project Control milestones and/or deliverables. The Lessons Learned document is used to identify and preserve the lessons learned on each project. The purpose of this document is to help the project team share knowledge *Lessons Learned 2.0 .doc Closure gained from the experience. A successful Lessons Learned program will help project teams repeat desirable outcomes and avoid undesirable outcomes. The Project Closure document formalizes the *Project Closure 2.0 .xlsx Closure completion of the project. *These templates are highly recommended when using PM Lite, regardless of project size or complexity.1 Section 3. PM Lite 2.0 Process The PM Lite 2.0 Process has five core phases and one pre-process phase. The five phases represent a typical project life-cycle. They include initiation, planning, executing, monitoring and controlling, and closure. The diagram below identifies which templates are typically created and/or completed during each phase of the project lifecycle. 3.1 Portfolio Review (Pre-Initiation) The Portfolio Review is a DIR internal process for prioritizing, aligning, and evaluating project requests. When the business idea is submitted by the Project Sponsor, the Portfolio Review Board reviews and assigns the project to a Project Manager based on prioritization and strategic alignment. 3.1.1 Business Case The Project Sponsor or Business Owner submits this template. This template will address the business issue and the expected business outcome as well as the key resources necessary for the project. It is defines how the project will align to the goals of the agency and/or state. 3.2 Initiation The Initiation Phase reviews the business idea and turns it into a formal project. 3.2.1 Key Activities: Review Lessons Learned from similar projects Identify project risks and constraints Define expected outcomes and key milestones Define high-level scope, schedule, and costs
Project Meeting Notes 2.0 .doc The Project Meeting Notes Template is used to document and communicate notes for all project meetings. Monitor & Control Project Status Report 2.0 .doc The Status Report is utilized for communicating the overall health of the project to the core team and key project stakeholders to keep everyone abreast of project progress. Monitor & Control Project Change Request 2.0 .doc The Project Change Request (PCR) is used by the Project Manager to request a change to the project scope, schedule, costs, project milestones and/or deliverables. Monitor & Control *Lessons Learned 2.0 .doc The Lessons Learned document is used to identify and preserve the lessons learned on each project. The purpose of this document is to help the project team share knowledge gained from the experience. A successful Lessons Learned program will help project teams repeat desirable outcomes and avoid undesirable outcomes. Closure *Project Closure 2.0 .xlsx The Project Closure document formalizes the completion of the project. Closure *These templates are highly recommended when using PM Lite, regardless of project size or complexity.1 Section 3. PM Lite 2.0 Process The PM Lite 2.0 Process has five core phases and one pre-process phase. The five phases represent a typical project life-cycle. They include initiation, planning, executing, monitoring and controlling, and closure. The diagram below identifies which templates are typically created and/or completed during each phase of the project lifecycle. 3.1 Portfolio Review (Pre-Initiation) The Portfolio Review is a DIR internal process for prioritizing, aligning, and evaluating project requests. When the business idea is submitted by the Project Sponsor, the Portfolio Review Board reviews and assigns the project to a Project Manager based on prioritization and strategic alignment. 3.1.1 Business Case The Project Sponsor or Business Owner submits this template. This template will address the business issue and the expected business outcome as well as the key resources necessary for the project. It is defines how the project will align to the goals of the agency and/or state. 3.2 Initiation The Initiation Phase reviews the business idea and turns it into a formal project. 3.2.1 Key Activities: Review Lessons Learned from similar projects Identify project risks and constraints Define expected outcomes and key milestones Define high-level scope, schedule, and costs
PM%20Lite%20Process%20Documentation%202.0.docx