Project Plan

Learning Objectives

1. Define project planning and the role of a project plan

2. Identify the core elements/components of a project plan
3. Describe the steps and techniques used in project planning
4. Apply planning techniques (WBS, schedule, risk management, stakeholder mapping) in
a sample project
5. Understand how to monitor, adjust, and control a project plan during execution

1. Introduction & Importance of Planning

• What happens when you don’t plan?

• What benefits come from good planning?

Planning is foundational: it clarifies who, what, when, how, why throughout the project lifecycle

Solid project plan helps with monitoring, controlling scope, avoiding surprises, aligning
stakeholders

2. What Is Project Planning & Project Plan

Project planning: the process of defining goals, timeline, tasks, resources, and strategy to
execute the project.

Project plan (or project management plan): a formal document (or set of documents) that
describes how the project will be executed, managed, controlled, and closed. It includes scope,
schedule, cost, quality, risk, procurement, stakeholder, etc.

Project plan is more than a Gantt chart: it’s the overarching blueprint for all project
governance and operations.

Key Sub-Documents

• Project Charter
• Statement of Work (SOW)
• Work Breakdown Structure (WBS)
• Various management plans: scope, schedule, cost, risk, communications, quality,
procurement, stakeholder, change management

Management of Engineering Projects |1

3. Core Elements / Components of a Project Plan

Here are the essential elements to include in a project plan

Component Description / Purpose Key Questions to Answer

Scope & What is (and what is not) What are the boundaries? What
Deliverables included in the project; what are the deliverables? What is
products or outcomes will be excluded?
produced
Schedule / Timeline When tasks will be done, What tasks? What order?
milestones, dependencies Duration? Dependencies?
Milestones?
Resources & Roles Who (people), what What resources are needed?
(equipment, materials), how Who will do which tasks? What
much constraints?
Cost / Budget Estimated cost for tasks, What is the cost of resources?
contingency, baseline What is allowed for
contingencies?
Risk Management What risks might occur, how to What could go wrong? What’s
respond, who owns them the probability & impact? What
are mitigation / contingency
plans?
Stakeholder & Who cares? How and when will Who are stakeholders? What
Communication communication occur? are their needs? What
Plan communication channels &
frequency?
Quality What quality standards or How do we assure and control
Management criteria must be met? quality? What metrics or
criteria?
Procurement / External purchases, contracts, What needs to be acquired?
Contracting vendors How? Under what terms?
Change How changes will be handled What is the process for change
Management / (scope, schedule, cost) requests? Who approves them?
Control How to document changes?

4. Project Planning Steps & Techniques

High-Level Steps to Create a Project Plan

1. Define the project scope

2. Create the project schedule / timeline
3. Identify required resources
4. Estimate costs and establish the budget
5. Identify stakeholders and plan engagement
6. Identify risks and define responses
7. Plan communications

Management of Engineering Projects |2

 8. Plan procurement
9. Establish quality assurance & control
10. Define change control process

Techniques / Tools for Planning

• Work Breakdown Structure (WBS): breaking down the project into phases, deliverables,
work packages. Ensures no critical tasks are missed.
• Gantt Charts / Network Diagrams: for scheduling, showing dependencies, timelines.
• PERT / Estimate Techniques: using optimistic, pessimistic, and most likely estimates. (if
applicable)
• Risk Matrix / Risk Register: mapping risks by likelihood and impact, assigning owners,
mitigation strategies
• Stakeholder Mapping / Analysis: categorize stakeholders by influence / interest
• Resource Leveling / Resource Smoothing: to avoid over allocation
• Iteration & Rolling Wave Planning: planning in detail for near tasks, leaving further tasks
more flexible

5. Managing and Adjusting the Plan

• A project plan is not static; it should be revisited and updated as the project evolves.
• During execution, tasks may slip, risks may materialize, scope may change, the project
manager must monitor, control, and adapt.
• Use metrics and baselines (schedule baseline, cost baseline) as reference points.
• Reassess the critical path periodically, because it can shift with delays or accelerations.
• Handle change requests using a formal change control process.
• Communicate with stakeholders when changes are made: what changed, why, impact
on timeline, cost, and quality.
• Encourage flexibility but with discipline—balance adapting vs scope creep.

6. Tips, Best Practices & Common Pitfalls

• Best Practices / Tips

• Involve the team and stakeholders early to get realistic estimates and buy-in
• Use historical data or expert judgment for estimates
• Be realistic and conservative: guard against over-optimism
• Leave buffer (float) time in schedule for uncertainty
• Keep the plan simple and understandable—avoid undue complexity
• Use tools / software (Gantt, dashboards) to keep visibility and collaboration
• Review and adjust often; treat the plan as a living document
• Maintain strong change control

Management of Engineering Projects |3

 • Communicate clearly and regularly

Common Pitfalls to Avoid

• Omitting key tasks or deliverables (scope gaps)

• Overlooking dependencies
• Underestimating resource constraints
• Ignoring risk or not planning mitigation
• Allowing uncontrolled changes (scope creep)
• Overcomplicating the plan so no one understands it
• Letting the plan sit unused—i.e. not referring to it or updating it

Management of Engineering Projects |4

Work Breakdown Structure

Work Breakdown Structure (WBS) is the tool that utilizes this technique and is one of the most
important project management documents. It singlehandedly integrates scope, cost and
schedule baselines ensuring that project plans are in alignment. Breaking work into smaller
tasks is a common productivity technique used to make the work more manageable and
approachable.

Importance of Work Breakdown Structure in Project

Management

Management of Engineering Projects |5

 1. Visuality

The Work Breakdown Structure is a visual tool. As such, it helps in creating an image of
what the project entails, in a clear and vivid manner. Visualising the individual steps and
processes helps the users see the “big picture” of the project.

2. Complexity

Another great feature of the Work Breakdown Structure is its complexity. It consists of
all the work steps, activities and tasks of the project and therefore is very detailed. This
may seem confusing to first-time users, yet the complexity means all the nuances are
taken into consideration.

3. Hierarchy

Another great feature of the Work Breakdown Structure is that it anticipates the
hierarchy and portrays the high-level project as well as possible sub-projects, work
packages, and individual tasks for team members.

4. Clarity

While the Work Breakdown Structure may end up being confusing, it offers a great deal
of insight and shows often overlooked aspects of the given project. On the other hand, it
reveals the area that might need to be cut or outsourced for better performance. Thus,
visualisation through the Work Breakdown Structure helps gain clarity on the exact
scope of the project.

Management of Engineering Projects |6

Types of WBS

Deliverable-Based Work Breakdown structure

If the WBS is primarily based on the deliverables of the project, then the structure is
deliverable oriented. The main units will consist of the main groups of deliverables, such
as individual services offered, and products delivered. By using this deliverable-based
approach, managers can make more accurate resource and budget estimations
because they can see all the project’s levels.

The Level 1 Elements are summary deliverable descriptions. The Level 2 Elements in
each Leg of the WBS are all the unique deliverables required to create the respective
Level 1 deliverable.

2. Phase-Based Work Breakdown Structure

This phase-based structure focuses on the individual project phases and organising all
activities in a chronological way. The project phases typically include the planning,
execution, control and closeout. This way of defining a WBS, like steps that need to be
taken to accomplish a goal, has the benefit of creating a more coherent project scope.

Management of Engineering Projects |7

the Level 1 has five Elements. Each of these Elements are typical phases of a project. The
Level 2 Elements are the unique deliverables in each phase. Regardless of the type of WBS,
the lower Level Elements are all deliverables. Notice that Elements in different Legs have the
same name.

Management of Engineering Projects |8