Foundations of Project Management

Every failed project shares a common ancestor: a weak foundation. Before a single Gantt bar is drawn or a budget line is approved, the project manager must command a deep understanding of the frameworks, structures, and methodologies that govern the discipline. This is not academic theory — it is the operating system upon which every successful project runs.

This article is the bedrock. Master it, and everything that follows — from initiating to closing — will click into place.

---

Why Foundations Matter

Projects do not fail during execution. They fail during conception. A project manager who does not understand the difference between a process group and a project phase, or who cannot articulate where their organisation sits on the maturity spectrum, is navigating without a map.

Core Principle: Project management is not about managing tasks. It is about managing constraints — time, cost, scope, and quality — within an organisational context that is rarely ideal.

The PMBOK® Guide (5th Edition) provides the universal language for this discipline. Whether you are relocating a zoo, building a warship, or deploying enterprise software, the constructs remain the same.

---

What is a Project?

Definition: A project is a temporary endeavour undertaken to create a unique product, service, or result. — PMBOK® Guide, 5th Edition

Two words carry all the weight here: temporary and unique. If it is ongoing and repetitive, it is operations. If it has a defined beginning, a defined end, and produces something that did not exist before — it is a project.

---

The Project Context

Projects do not exist in a vacuum. They are initiated in response to forces that include business needs, stakeholder pressure, technological obsolescence, market demand, and regulatory change. Understanding the why behind a project is the first step in managing it effectively.

A business case is created to determine whether the project is worth the investment. This is built on factors such as market demand, social need, ecological impacts, and organisational need — but notably, availability of funds is not a criterion for the business case itself. Funding is a constraint, not a justification.

---

Organisational Structures

The structure of the organisation hosting the project has a direct impact on the project manager's authority, resource access, and communication pathways.

Exam Tip: A matrix organisation is best suited for complex projects because it blends functional expertise with dedicated project management focus. However, team building is most difficult in a matrix structure because team members report to multiple managers.

CEO / Senior Management

Functional Manager A

Functional Manager B

Project Manager

Team Member 1

Team Member 2

Team Member 3

Team Member 4

Relationship details

From	Relationship	To
CEO / Senior Management	leads to	Functional Manager A
CEO / Senior Management	leads to	Functional Manager B
CEO / Senior Management	leads to	Project Manager
Functional Manager A	leads to	Team Member 1
Functional Manager A	leads to	Team Member 2
Functional Manager B	leads to	Team Member 3
Functional Manager B	leads to	Team Member 4
Project Manager	Dotted-line authority	Team Member 1
Project Manager	Dotted-line authority	Team Member 3
Project Manager	Dotted-line authority	Team Member 4

---

The PMBOK® Guide Framework

The PMBOK® Guide establishes three interconnected constructs for managing a project:

1. Project Lifecycle Phases
2. Project Process Groups
3. Project Management Knowledge Areas

These are not the same thing — confusing them is a common and costly mistake.

---

The Project Lifecycle

The project lifecycle describes the phases a project passes through from beginning to end. Each phase produces key deliverables that serve as the foundation for the next.

Phase 1 — Starting the — Project

Phase 2 — Organising & — Preparing

Phase 3 — Carrying Out — the Work

Phase 4 — Closing the — Project

• Project Proposal — • Project Charter

• Project Management — Plan

• Progressive Completion — • Practical Completion

• Project Finalisation — • Documentation — & Reports

Relationship details

From	Relationship	To
Phase 1 — Starting the — Project	leads to	Phase 2 — Organising & — Preparing
Phase 2 — Organising & — Preparing	leads to	Phase 3 — Carrying Out — the Work
Phase 3 — Carrying Out — the Work	leads to	Phase 4 — Closing the — Project
• Project Proposal — • Project Charter	leads to	Phase 1 — Starting the — Project
• Project Management — Plan	leads to	Phase 2 — Organising & — Preparing
• Progressive Completion — • Practical Completion	leads to	Phase 3 — Carrying Out — the Work
• Project Finalisation — • Documentation — & Reports	leads to	Phase 4 — Closing the — Project

Key Distinction: The review of deliverables and performance at the conclusion of a project phase is known interchangeably as a phase exit, kill point, or stage gate. Its purpose is to determine whether the project should continue to the next phase — or be terminated.

---

Project Process Groups

Complementary but separate to project phases, the PMBOK® Guide groups project processes into five distinct process groups.

Critical Rule: Process Groups are NOT the same as Project Phases. A single phase may involve processes from multiple groups, and a single process group may span multiple phases.

Starting

Organising

Executing

Closing

overlapping

Initiating

Planning

Executing

Monitoring & Controlling

Closing

Relationship details

From	Relationship	To
Starting	leads to	Organising
Organising	leads to	Executing
Executing	leads to	Closing
Monitoring & Controlling	Spans entire lifecycle	Starting
Monitoring & Controlling		Organising
Monitoring & Controlling		Executing
Monitoring & Controlling		Closing

The Five Process Groups — Key Processes

Initiating: Develop Project Charter, Identify Stakeholders.

Planning: This is the largest group. It includes Develop Project Management Plan, Plan Scope Management, Collect Requirements, Define Scope, Create WBS, Define Activities, Sequence Activities, Estimate Activity Resources, Estimate Activity Durations, Develop Schedule, Plan Cost Management, Estimate Costs, Determine Budget, Plan Quality Management, Plan Human Resource Management, Plan Communications Management, Plan Risk Management, Identify Risks, Perform Qualitative and Quantitative Risk Analysis, Plan Risk Responses, Plan Procurement Management, and Plan Stakeholder Management.

Executing: Direct and Manage Project Work, Perform Quality Assurance, Acquire Project Team, Develop Project Team, Manage Project Team, Manage Communications, Conduct Procurements, Manage Stakeholder Engagement.

Monitoring & Controlling: Monitor and Control Project Work, Perform Integrated Change Control, Validate Scope, Control Scope, Control Schedule, Control Costs, Control Quality, Control Communications, Control Risks, Control Procurements, Manage Stakeholder Engagement.

Closing: Close Project or Phase, Close Procurements.

---

The PDSA Cycle — Continuous Improvement in Projects

Complementary to the PMBOK process groups, Deming's Plan-Do-Study-Act (PDSA) Cycle explains how project processes improve through repetition.

PLAN

DO

STUDY

ACT

Relationship details

From	Relationship	To
PLAN	leads to	DO
DO	leads to	STUDY
STUDY	leads to	ACT
ACT	Continuous — Improvement	PLAN

Business Value: The PDSA cycle illustrates that a process or product should always get better as knowledge and experience accumulate over time. Each repetition of the cycle drives further improvement — the foundation of lean and quality management in heavy engineering environments.

Starting

Organising

Executing

Closing

Plan

Do

Study

Act

Plan

Do

Study

Act

Plan

Do

Study

Act

Relationship details

From	Relationship	To
Starting	leads to	Organising
Organising	leads to	Executing
Executing	leads to	Closing
Plan	leads to	Do
Do	leads to	Study
Study	leads to	Act
Act	leads to	Plan
Plan	leads to	Starting
Plan	leads to	Organising
Plan	leads to	Executing
Act	leads to	Closing

---

Project Management Knowledge Areas

To effectively manage all processes within a project, the PMBOK identifies ten knowledge areas. Each represents a critical domain of expertise.

The Core Project Constraint Triangle

The four core elements — Time, Cost, Quality, and Scope — are interdependent. Changing one always impacts the others. Scope sits at the centre as the most foundational element.

TIME

COST

QUALITY

SCOPE

Integration

Stakeholders

Communication

Risk

HR

Procurement

Relationship details

From	Relationship	To
TIME	leads to	COST
COST	leads to	QUALITY
QUALITY	leads to	TIME
SCOPE	leads to	TIME
SCOPE	leads to	COST
SCOPE	leads to	QUALITY
Integration	leads to	Stakeholders
Stakeholders	leads to	Communication
Communication	leads to	Risk
Risk	leads to	HR
HR	leads to	Procurement
Procurement	leads to	Integration
Integration	leads to	TIME
Stakeholders	leads to	QUALITY
Communication	leads to	COST
Risk	leads to	SCOPE
HR	leads to	TIME
Procurement	leads to	COST

The Iron Rule: You cannot increase scope without increasing time or cost (or both), and you cannot reduce time without either increasing cost or reducing scope/quality.

---

Common Pitfalls

Confusing Process Groups with Phases. They are parallel constructs, not synonyms. The Monitoring & Controlling process group, for example, runs across all lifecycle phases.

Ignoring Organisational Context. A PM in a weak matrix has fundamentally different authority and resource access than one in a projectised structure. Your approach must adapt accordingly.

Treating the PMBOK as a Checklist. The PMBOK is a guide, not a prescription. Tailor processes to the size, complexity, and risk profile of your project.

Underestimating Communication. A typical project manager spends 75–90% of their time communicating — formally and informally — with stakeholders, sponsors, customers, vendors, and the project team.

Skipping the Business Case. Without a clear justification rooted in business need, even a well-managed project can deliver the wrong outcome.

---

Key Takeaways

• A project is a temporary endeavour producing a unique output — distinguish it from operations.
• The PMBOK® Guide provides three interlocking constructs: lifecycle phases, process groups, and knowledge areas.
• Process Groups ≠ Project Phases — this is the most commonly tested distinction.
• Organisational structure directly impacts PM authority — matrix is best for complex projects but hardest for team building.
• The PDSA cycle drives continuous improvement across all project phases.
• The four core constraints — time, cost, quality, scope — are inseparable. Change one, and the others shift.
• The project manager is the critical communication element in every project.