Project Planning

Any project requires planning. This document outlines detailed directions that can be followed by the project team throughout the entire project duration.

Why

Creating a project baseline plan can be broken down into six steps:

1. Determine activities - Identify the activities needed to produce the deliverable. Verbs and objects are best used to describe deliverables.

2. Estimate the resource requirements and durations - When completing an activity, estimate the resources required to complete the activity and the time it will take to complete the activity.

3. Creating a schedule model - All of the information gathered in the first two steps is integrated into this step. The order in which activities must be completed, the resources required, and the resources required for completion are listed on the schedule. It is recommended that a management software program be used.

4. Request approval - Establishing steering committees will be necessary to get approval.

5. Establish a schedule baseline and communicate it - The RACI acronym stands for responsible, accountable, consulted, and informed, which can reveal those who need to be informed

6. Maintain the schedule baseline - The schedule baseline can be used to determine how successful a project has been after it is launched

The project launch meeting will take place during the early stages of planning. The objective of a launch meeting is to demonstrate the commitment of top management to the project. A well-defined set of objectives is crucial to the success of the launch meeting. It isn't wise to spend excessive time on planning, scheduling, or budgets beyond the most basic level at the launch meeting, as the project may not take off at all. A project launch meeting will occur during the planning phase.

Project Scope Management

An individual project's scope describes all the work involved in completing it. Plan, define, and control what is or is not included in a project.

The creep and leap of project

The creep of the project scope determines whether it will likely change and by how much and how often. The changes will be minor.

Leaps are significant changes to the project. The project is substantially changed.

Composite Plan

Developed from the Project Launch Meeting, the composite plan is a draft of what has been outlined. All participants must approve it, including the manager of the project as well as all the senior management within the organization.

A change order must be submitted at each stage when the plan is approved by Senior Management and is countersigned by them.

Whenever a change in the project's scope is made, it must be processed as a formal change order (project scope change order) when it has been approved by further approvals. A responsibility matrix should be developed by each individual or unit that accepts responsibility for a portion of the project (responsibility matrix) so that initial plans can be developed for how the responsibility will be met.

A plan should include a description of the required tasks, as well as estimated budgets and schedules. The group scrutinizes these plans and combines them into a composite project plan (project base line).

Project Initiation Document

During the project initiation process, the scope of the project, the collaborative information, and the success criteria are provided. The document should be written and explained in a way that is easily understood by all parties.

A Project initiation document must have the following features

• Project Justification

• Defining the Project

• Assumptions

• Business Case

• Organisation

• Communication Plan

• Quality Management Plan

• Project Management Plan

• Measures

• Log of Risks

• Plan of Action

• Structure of the documentation.

Hierarchical planning system

This system concludes the project planning lessons. This way, tasks are arranged in a hierarchical way. It is also possible to plan them simultaneously or in sequential order. They may be organized in parallel or in succession. From start to finish, and in between, a hierarchical system tells the project's tasks.

Creating a WBS with a hierarchical planning system

WBSs or work breakdown structures are foundation documents. This is created by using the hierarchical planning system since it can be divided up into different sections, projects, summary tasks, and subtasks. An example can be used to demonstrate how each component contributes to the project in terms of performance, responsibility, schedule, and budget. Members can be assigned tasks and this can be monitored.