In the PLAN phase, the team designs the selected project. Most of the work performed in PLAN becomes the foundation for implementation and post implementation management and it helps guide successful completion of essential project work. Here, the project team estimates and establishes the scope of work, defines and refines the project objectives, develops the course of actions to attain those objectives, and establishes methods for managing and controlling the project.
During PLAN, the project manager on-boards the project team. A formal kick of meeting may be needed if the project is large and/or complex.
The first formal step in planning is determining the current state, if it hasn’t already been mapped, and illustrating the desired future state. This is accomplished through a business process reengineering (BPR) evaluation – which documents the current processes and business needs, and identifying where waste, redundancy, and inefficiency may exist. Thereafter, the focus shifts to identifying the desired future state and analyzing the gaps between the “as is” and “to be” states. BPR does not eliminate all manual processes and some new processes may be a combination of manual and automated activities.
The sponsor and project manager, with assistance from other key participants, diagram the current state and the desired future state. These diagrams are used to help define the depth and breadth of organizational change that will likely need to occur. In projects involving end user organizational change in multiple agencies, each agency should conduct its own development of process maps upon commencement of its portion of the project. The process diagrams can be attached to the task in your project management software
Participants from the diagramming event should also develop an outline of key process changes and other factors that will need to occur during implementation and document them in the project plan for later reference. This can be accomplished in tandem with process mapping. Dependencies should be highlighted to ensure that critical steps are not overlooked. Similarly, stakeholders not immediately involved in the process should be considered in the event that a process change in one function has a significant impact on another.
Participants are encouraged to use a benefits dependency network diagram or similar tool, to illustrate the logical relationship between and among desired outcomes and other tasks that have a direct or indirect relationship to a project benefit and which must occur in order for the benefit or outcome to be achieved. The benefits dependency network diagram is retained in the project record.
The project manager, in consultation with the project sponsor outlines the project deliverables and documents them in the project plan. A deliverable is a unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project. A deliverable is a work product produced by a project team, team member, contractor, or consultant in accordance with the terms of their requirements or contract.
As a component of deliverables, the project team documents requirements. Requirements grow out of the product vision, which in turn, is driven by mission, or business goals and objectives. Requirements can also be a condition or capability that is required to be present in a product, service, or result to satisfy a contract or other formally imposed specification. These may be used to evaluate to what extent a solution offered addresses the problem. Deliverables and requirements are maintained in the project documentation.
The project team, in consultation with the project sponsor and key participants and business/process representatives, identify measurable benefits/key performance indicators (KPIs). These measures are essentially measures of success that may be underlain by KPIs or lower level metrics (value) and are documented in the value register. They will be used to ascertain if the solution is performing as desired. The benefits toolkit or a similar template can be attached to the task in your project management software, or may be submitted with your phase review information.
The project team and change manager develop an organizational change management (OCM) plan which is a structured approach to shifting or transitioning an organization from the current state to a desired future state. Project teams may use the OCM toolkit or an agency specific tool for development of the OCM plan.
The OCM Plan contains a communication plan and project teams may use the communications plan toolkit or an agency specific template. The communications plan defines and documents the project communication requirements and the approach for how information will be distributed. It describes the communication needs and expectations for the project; how and in what format information will be communicated; when and where each communication will be made; and who is responsible for providing each type of communication. The plan should be developed in coordination with, and be accessible to, all stakeholders.
Using internal or external resources, the project team and sponsor conduct market research to gather information about potential solutions. Market research is a key factor in maintaining competitiveness. Market research provides important information to identify and analyze the market competition. Project teams should document the market research in a manner consistent with the market research guide and attach the results to the task in your project management software and submit it with your phase review information
Once market research has been completed, the project team analyzes alternatives. This entails breaking down a complex situation to generate different solutions and approaches in order to evaluate the impact of trade-offs. Various alternatives are often based on the results of the market research. You should document the alternatives analysis in a manner consistent with the alternatives analysis guide and attach the results to the task in your project management software and submit it with your phase review information.
After the project team, sponsor and steering committee have studied and selected a preferred approach, the project team develops the acquisition plan, which documents cost, schedule, technical, business, management, and other considerations that will govern an acquisition program. It summarizes the acquisition planning discussions and identifies milestones in the acquisition process. A successful acquisition is based on a sound sourcing strategy and the development of the sourcing strategy requires a thorough understanding of the project, a conceptual understanding of the resources required to deliver that strategy and the market forces that the sourcing strategy will utilize.
Once the acquisition plan is complete, the team begins to develop the procurement documents (RFx) in accordance with state and agency policy.
In conjunction with developing the acquisition plan the project team develops and documents acceptance criteria which are the performance requirements and essential conditions that must be achieved before acceptance of project deliverables. You should document the acceptance criteria in a manner consistent with the developing and using acceptance criteria guidance or your agency practice.
The sponsor approves the required PLAN deliverables and the project manager submits the materials to agency governance for review. The PLAN phase review is a formal examination of planning deliverables to ensure the project is well planned and basic project management principles have been applied before advancing to the next phase of the project.
The project team receives a confirmation of receipt of deliverables and, upon completion of the review, a disposition. At the completion of the PLAN phase, approval to proceed releases funding for the EXECUTE and BUILD phase.
After the PLAN phase has been reviewed and approved, the project team releases a request for services to the market. The RFx may be developed during the sourcing strategy and acquisition plan development and should accompany the PLAN phase deliverables for review by governance before being released to the market.