1. Strategic role of the Planning process group

If Initiating is where we answer “Why does the project exist and who owns it?”, then Planning is where we answer “How can we achieve the objectives with available resources?”.

In the PMBOK® Guide by the Project Management Institute – PMI (USA), Planning is considered the most critical process group, taking about 60–70% of the project manager’s thinking effort.

Poor or superficial planning means accepting that the project will drift with improvisation, easily fall behind schedule, overrun cost and lose control of quality.

2. Objectives of Planning

The core objectives of the Planning process group include:

• Clarifying the project scope – what will be done and what will not.
• Designing a realistic and logical roadmap with measurable milestones.
• Anticipating risks and preparing response strategies.
• Defining quality, cost, resource, communication and procurement expectations.
• Establishing baselines to compare, control and adjust later.

The final outcome is a comprehensive Project Management Plan – a detailed roadmap that guides the project team throughout the project life cycle.

3. Key components of Planning

3.1. Developing the Project Management Plan

According to PMBOK®, the Project Management Plan is an integrated document that consolidates all subsidiary management plans. At a minimum, a project should have:

• Scope Management Plan – how scope is defined, approved and controlled.
• Schedule Management Plan – how the schedule is developed, updated and reported.
• Cost Management Plan – how cost estimates, budgets and controls are handled.
• Quality Management Plan – standards, acceptance criteria and quality processes.
• Communications Management Plan – who needs what information, when and how.
• Risk Management Plan – methods for risk identification, analysis and response.
• Resource / Human Resources Management Plan – roles, responsibilities, RACI matrix, competency requirements.
• Procurement Management Plan – procurement strategies, contract types, selection criteria.

???? Official reference: PMBOK® Guide & Standards – PMI

3.2. Building the Work Breakdown Structure (WBS)

The Work Breakdown Structure (WBS) breaks the project down into smaller, more manageable components until each work package can be planned, measured and assigned.

Main benefits of WBS:

• Provides both a big picture and detailed view of project work.
• Forms the basis for cost, time and resource estimates.
• Reduces the chance of missing critical tasks.
• Provides a structure for documentation, acceptance and project closeout.

3.3. Scheduling with network diagrams, CPM and Gantt charts

Once the WBS is defined, the next step is to position activities on the time axis and establish logical relationships. Common tools include:

• Network Diagrams – show activities and dependencies (FS, SS, FF, SF).
• Critical Path Method (CPM) – identifies the path that determines the project’s total duration.
• Gantt Charts – bar charts that visualise schedule over time, easy to present to stakeholders.

A good schedule not only “looks nice on paper” but also reflects resource constraints, site conditions, weather and technical realities.

3.4. Establishing baselines for scope, schedule and cost

When scope, schedule and cost are agreed and approved, we establish the corresponding baselines:

• Scope Baseline – the approved project scope.
• Schedule Baseline – the approved project schedule.
• Cost Baseline – the approved cost baseline.

Baselines are the official starting point for later comparison and control in the Monitoring & Controlling process group (Article 4/5).

Any major change request affecting scope, time or cost should be processed through a formal change control procedure and baselines updated once approved.

3.5. Risk register and response planning

Planning is not just about optimistic scenarios – it is about being prepared for what could go wrong.

Typical PMBOK® steps include:

• Risk identification.
• Qualitative and/or quantitative analysis.
• Building a risk register – causes, impacts and risk owners are clearly documented.
• Developing risk response plans – avoid, mitigate, transfer or accept.
• Ongoing monitoring and updating during the project.

A Probability–Impact matrix helps prioritise attention and resources on high–probability, high–impact risks instead of spreading efforts too thinly.

4. Practical meaning for businesses & INDUSVINA projects

When Planning is done properly, the project gains clear advantages:

• The team understands objectives, scope and roles clearly.
• Management decisions are based on data and plans, not gut feeling only.
• Risks of delays, cost overruns and internal conflicts are reduced.
• Higher likelihood of doing things right the first time, saving total life–cycle cost.

This is also where the professional level of the project manager is revealed: someone who merely “chases problems” is very different from someone who anticipates, plans and leads.

5. Connection with the PMBOK series at INDUSVINA

This article is Article 2/5 – Planning in the series “5 Project Management Process Groups According to PMBOK (PMI – USA)” published by INDUSVINA.

If you have not read them yet:

• ???? Overview article: 5 Project Management Process Groups According to PMBOK (PMI – USA)
• ???? Article 1/5 – Initiating: https://indusvina.com/bai-1-5-initiating-khoi-tao-du-an.htm

Upcoming articles in the series:

• Article 3/5 – Executing
• Article 4/5 – Monitoring & Controlling
• Article 5/5 – Closing

6. A note of thanks from INDUSVINA

Thank you for spending your time reading and learning with INDUSVINA Knowledge Hub.

We encourage you to share this article with colleagues and friends so that more professionals can work with discipline and international standards.

Any feedback or questions about PMBOK, project management or technical/legal topics in construction are most welcome – every comment from you is a valuable asset that helps us improve.

INDUSVINA – Discipline Creates Strength.