Project planning is the stage where a project is carefully thought through
before serious work begins. At its core, it is a series of organized activities
that clearly explain what must be done, how it will be done, where it will take
place, and when each activity should happen. Instead of guessing or working
blindly, project planning gives direction and order to the entire project.
From a management point of view, project planning is a process carried out
by the project team to understand the purpose of the project, how much it
will cost, how long it will take, and the procedures that will be followed. This
ensures that everyone involved understands why the project exists and what
is required to complete it successfully. In this sense, project planning acts like
a roadmap for the whole project lifecycle. It defines the objectives, scope,
deliverables, timelines, resources, and activities so that the project can move
from an idea to a completed outcome in a structured way.
Project planning can also be described as a blueprint. Just as an architect’s
blueprint shows what a building should look like and how it will be
constructed, a project plan shows the goals, objectives, and tasks that the
team must accomplish. It is during this phase that actual steps are
determined. This includes setting timelines, preparing a budget, identifying
milestones, assessing risks, breaking work into tasks, and assigning
responsibilities to team members. Without proper planning, projects often
face delays, cost overruns, or failure.
A key part of project planning is defining goals and objectives. Goals explain
why the project is being initiated and what benefits are expected, including
returns on investment. They describe the broad, long-term outcomes the
project aims to achieve. Objectives, on the other hand, are more specific.
They are measurable and actionable steps that help achieve those goals. For
example, a goal may be to improve housing delivery, while an objective may
be to construct 100 affordable housing units within two years.
Another important component is setting success metrics. These metrics help
answer the question: How do we know the project has been successful?
Success metrics are usually SMART, meaning they are specific, measurable,
achievable, relevant, and time-bound. For instance, completing a project
within budget and schedule can be used as clear indicators of success.
Project planning also requires clarifying stakeholders and their roles. This
involves identifying everyone who has an interest in the project, mapping
stakeholders according to their influence and interest, and clearly dividing
roles and responsibilities. When roles are unclear, conflicts and duplication of
effort often arise, which can harm project performance.
Setting the project budget is another crucial element. Based on the tasks
identified and the stakeholders involved, planners estimate the total cost
required to complete the project. This includes costs for labor, materials,
equipment, and administrative activities. A realistic budget helps prevent
financial problems during implementation.
Project plans also define milestones and deliverables. Milestones are key
points used to measure progress, while deliverables are the tangible outputs
achieved when milestones are reached. For example, completing the
foundation of a building can be a milestone, while the finished foundation
itself is a deliverable.
Closely related to this are timelines and schedules. These specify the time
periods within which activities must be completed. The level of detail in the
schedule depends on how much information is available at a given time.
Early planning may use broad timelines, while later stages require more
detailed schedules.
A communication plan is also part of project planning. This explains when
information will be shared, what information will be shared, how it will be
communicated, who will receive it, and for what purpose. Effective
communication ensures coordination, transparency, and accountability
throughout the project.
To develop and manage project plans, several methods of project planning
are used. One common method is the Critical Path Method (CPM). In CPM,
activities are connected based on their dependencies and arranged in a
network. Forward and backward calculations are used to identify the longest
sequence of dependent activities, known as the critical path. This path
determines the shortest possible project duration. Software such as
Primavera P6 or Microsoft Project is often used, especially for large projects
with thousands of activities.
Another widely used method is the Gantt Chart. In a Gantt chart, activities
are shown as horizontal bars. The length of each bar represents the duration
of the activity, while the start and end of the bar show when the activity
begins and finishes. This method is simple to understand and is useful for
tracking progress over time.
The Work Breakdown Structure (WBS) is another essential planning tool. It is
a hierarchical structure that breaks the entire project scope into smaller,
manageable parts. At the top level is the overall project. This is then divided
into major components or trade packages, followed by work packages, and
finally individual activities. The WBS ensures that no part of the project is
overlooked and provides a clear basis for scheduling, costing, and resource
allocation.
Linked to the WBS is the Organisational Breakdown Structure (OBS). The OBS
shows responsibility levels within the organization and explains reporting
relationships. It helps clarify who is responsible for which part of the work.
Within the WBS, the smallest unit is the project activity. An activity consumes
time, resources, and money. Activities can be production activities, such as
excavation or concreting, which involve labor, equipment, and materials.
They can also be procurement activities, which focus on acquiring materials
or equipment needed for production. Management activities relate to
decisions, approvals, and administrative processes.
The size and detail of activities depend on the stage of planning, the size of
the project, its complexity, and the experience of the management team.
Early stages may use broader activities, while construction stages require
detailed activities for effective control.
Activities are not independent; they have relationships. Some activities must
be completed before others can start, some can run at the same time, and
some must follow others. For example, site clearing must occur before
excavation. Utility installation may depend on trench excavation and grading.
These logical relationships ensure work is done in the correct order and
resources are used efficiently.
Resource availability also affects activity relationships. When resources are
constrained, only limited units are available, which may force activities to be
done sequentially. When resources are unconstrained, activities can proceed
concurrently if logic allows.
There are four main types of activity relationships. In a finish-to-start
relationship, a successor activity can only begin after the current one
finishes. In finish-to-finish, the successor cannot finish until the current
activity finishes. In start-to-start, the successor starts when the current
activity starts. In start-to-finish, the successor cannot finish until the current
activity has started.
To visualize these relationships, project network techniques are used. A
project network diagram graphically shows activities and their relationships,
including start and finish points. Activities at the start have no predecessors,
while those at the end have no successors.
One type of network diagram is Activity on Arrow (AOA). In AOA, arrows
represent activities, and nodes represent the start and end points. The
length or shape of the arrow has no meaning. When activities depend on
each other, they share common nodes. Certain rules apply, such as using
unique numbering and avoiding backward arrows. Dummy activities, shown
as dashed lines with zero duration, are used to represent logical relationships
without adding time or cost.
Another type is Activity on Node (AON), also called the precedence diagram
method. Here, nodes represent activities, and arrows show the relationships
between them. This method clearly shows predecessors and successors and
allows overlaps and time lags between activities.
When comparing the two, AON is generally easier to draw and understand. It
does not require dummy activities and can represent all four types of
relationships. AOA, by contrast, mainly represents finish-to-start relationships
and is more limited in flexibility.
Overall, project planning brings structure, clarity, and control to a project. By
carefully defining objectives, activities, relationships, resources, and
timelines, it greatly increases the likelihood of project success.
