|
|
|
|
|
|
|
The purpose of the Business Transition Plan is to define the project and need for focus on business transition and organizational efforts. |
|
|
|
The Business Transition (BT) Planning Checklist should be utilized in the Planning Process. Use it to evaluate whether or not the Planning activities for Business Transition Management have been completed and the BT resource is ready to move on to the Executing Process of the project. |
|
|
|
This document is a step-by-step instructions intended to aid Business Transition resources through Business Transition activities associated with projects. |
|
|
|
The purpose of the Change Management Plan is to define and agree on how changes are to be coordinated within the project and organization. |
|
|
|
The primary purpose of communication is to mitigate the issues. Starting with an understanding of the problem/opportunity, business goals, and project scope, communication activities detail stakeholders, and key messages, strategies, and tactics to facilitate a successful project. |
|
|
|
The document outlines information to summarize your best practice research findings specific to your project, highlighting the specific, objective data that supports your findings. |
|
|
|
The document outlines information to summarize the feasibility for the change. |
|
|
|
The document provides detail areas to summarize the workforce demographic and human resource force (internal and external) that the organization is sensing now and the impact is has on the organization.
|
|
|
|
This plan helps to define critical success indicators and factors for change projects. These indicators and factors are measures that accurately reflect the critical aspects of organizational processes, functions, relationships, and outputs. This document identifies each critical change project indicators and factors. |
- Integrated Project Plan (IPP) *
|
|
The Integrated Project Plan (IPP) documents all core work plans and project facilitation plans, details the approved solution (as outlined in the business case), and incorporates the project charter, scope, and general concept, method, processes, activities, and philosophy of managing the project through planning, executing, and closing, detailing resources necessary for success. |
|
|
|
The purpose of the Issue Management Plan is to outline the recommended approach for identifying outstanding issues, tracking the progress of the resolution, and documenting the solutions. |
|
|
|
Approval of the Post-Implementation Review of business outcomes indicates an understanding and acceptance of the post-implementation results described in this deliverable. |
|
|
|
This template is to be used for monthly status reporting on a project. It summarizes the project in brief format that is shown to management and supervisors on the overall project status and project phases. |
|
|
|
The Requirements Management Plan is to establish and maintain an agreement with the customer and the project on the requirements, which represent the product scope that will be addressed by the project. |
|
|
|
The purpose of this document is to provide guidelines, tips, and techniques helpful in the requirements management process. |
|
|
|
Use this Requirements Traceability Matrix to associate project Requirements to the deliverables that satisfy them. |
|
|
|
This plan is a controlling document incorporating the change projects purpose, goals and objectives to perform necessary risk determination, assessment and management. |
|
|
|
The Stakeholder Needs document is used to record needs elicited from stakeholders and to begin the process of decomposing the needs into more detail. |
|
|
|
To identify and record the names and contact information of all stakeholders relevant to gathering, verifying, and/or approving the requirements of a project. |
|
|
|
To describe the users' critical requirements for the information system. |
| |
|
|
