The Project Lifecycle: From Concept to Handover

Why the Lifecycle Matters

Every project, regardless of size or sector, follows a predictable arc. A bridge, a software platform, a defence procurement program — each begins as an idea and ends with a handover. The project lifecycle is the structural backbone that prevents that arc from collapsing into chaos.

Understanding the lifecycle isn't academic trivia. It's the difference between a project manager who reacts to events and one who anticipates them. When you know where you are in the lifecycle, you know what decisions carry the most weight, where your budget is most vulnerable, and when stakeholder influence is at its peak.

Definition: The project lifecycle is a collection of sequential project phases whose name and number are determined by the control needs of an organisation or the organisations involved in a project.

---

What is a Project Deliverable?

Before we walk through the phases, we need a shared understanding of what each phase actually produces.

Definition: A project deliverable is any measurable, tangible, verifiable outcome, result, or item that must be produced to complete a project or part of a project.

Deliverables are the proof that work has been done. They are the milestones that gate decisions. Without clearly defined deliverables at each phase boundary, projects drift — and drift is where cost overruns are born.

---

The Four Phases of the Project Lifecycle

The PMBOK® Guide organises the lifecycle into four broad phases. Each has a distinct purpose, a set of actions, and defined deliverables.

1. Starting the Project — 'The Idea'

2. Organising & Preparing — 'Planning the Project'

3. Carrying Out the Work — 'Doing the Project'

4. Closing the Project — 'Handover'

Relationship details

From	Relationship	To
1. Starting the Project — 'The Idea'	leads to	2. Organising & Preparing — 'Planning the Project'
2. Organising & Preparing — 'Planning the Project'	leads to	3. Carrying Out the Work — 'Doing the Project'
3. Carrying Out the Work — 'Doing the Project'	leads to	4. Closing the Project — 'Handover'

---

Phase 1: Starting the Project — "The Idea"

This is where the project is born. An idea or concept is recognised, a sponsor justifies alignment with strategic goals, and the project manager receives formal authority to proceed.

The Project Proposal

The proposal is the business case at its most raw. It must address:

• What are the project objectives?
• What problems or needs does this initiative solve?
• How does it align with the corporate strategy?
• What business benefits will flow from the project?
• What is the "best guess" estimate of time, cost, and resources?
• What are the project risks — and what are the risks of not doing it?

Responsibility: Prepared by the Project Sponsor. Signed off by Executive Management.

The Project Charter

The charter evolves from the proposal and becomes the framework for the entire Project Plan. Its purpose is to:

• Define the scope of work
• Establish objectives and deliverables
• Define the broad strategies for delivery
• Align deliverables to business needs

Responsibility: Prepared by the Project Manager in consultation with the Sponsor. Signed off by the Project Sponsor.

Key Principle: The Project Manager must have the formal support of the Project Sponsor. Without this, the PM is managing without authority — a recipe for failure.

---

Phase 2: Organising and Preparing — "Planning the Project"

This is where the real architecture of the project takes shape. The project team is assembled, the Project Plan is developed, and financial approval is secured.

The Project Plan is the single most important document in the project manager's toolkit. It is the consolidated reference point used to monitor and control the project throughout its life. For large projects, it may be supported by subsidiary plans:

• Risk Management Plan (including a Risk Register)
• Key Deliverables and Milestones schedule
• Communication Management Plan
• Quality Management Plan
• Procurement/Contract Management Plan

Pre-Implementation Review: Before execution begins, the charter and plan must be validated, team capabilities reviewed, and formal approval to proceed obtained. This is the last "off-ramp" before significant resources are committed.

---

Phase 3: Carrying Out the Project Work — "Doing the Project"

This is the execution engine — where the plan meets reality. The project manager's role shifts from architect to conductor, orchestrating activities, managing contracts, and controlling the triple constraint.

The project manager must be proactive across two environments:

Internal Environment:

• Ensure the project is on schedule
• Manage contracts, risks, budget, and resources
• Monitor quality requirements
• Manage project change and lead the team

External Environment:

• Manage organisational interfaces
• Negotiate approvals
• Formally report project progress
• Manage stakeholder expectations

---

Phase 4: Closing the Project — "Handover"

The most frequently underestimated phase. Closing is not simply "finishing the work." It is a structured process of verification, transfer, and organisational learning.

Post-Implementation Review

This is where the organisation captures institutional knowledge. Activities include:

• Conduct the review against baseline (budget, schedule)
• Record lessons learned
• Review success criteria
• Facilitate a project audit
• Draft and submit the Project Completion Report (PCR)
• Formally transfer assets and archive documentation

Common Pitfall: Many organisations skip or rush the post-implementation review. This means the same mistakes are repeated on the next project. The cost of a two-day review is trivial compared to the cost of repeating a $5M error.

---

Lifecycle Characteristics: Three Critical Curves

The project lifecycle isn't just a sequence of phases — it has predictable behavioural characteristics that every project manager must internalise.

Lifecycle Dynamics Over Time

Qualitative visual—not a calibrated engineering scale.

Relationship	Initiation	Planning	Execution	Closure
Level of effort	20%	55%	100%	25%
Potential to add value	100%	75%	35%	10%
Relative cost of change	10%	25%	65%	100%

Three key dynamics:

1. Level of Effort follows a bell curve — low during initiation, peaking during execution, and tapering during close-out.
2. Potential for Adding Value is highest at the start and declines as the project progresses. Early decisions have the greatest leverage.
3. Stakeholder Influence is strongest early in the project and diminishes as commitments are locked in and the cost of changes escalates.

The Pareto Principle Applied: Approximately 80% of project costs are established in the first 20% of the project life. If you want to positively influence final cost, the design and planning phases are your window.

This is why front-end project controls — applied during design — offer the best opportunity to prevent overruns. By the time you're in construction or execution, the ability to influence cost has largely evaporated.

---

The Typical Sequence of Phases

💡 Idea

INITIAL Phase

INTERMEDIATE Phase

FINAL Phase

Charter — Scope Statement

Plan / Baseline — Progress / Acceptance

Approval — Handover — Product

Relationship details

From	Relationship	To
💡 Idea	leads to	INITIAL Phase
INITIAL Phase	leads to	INTERMEDIATE Phase
INTERMEDIATE Phase	leads to	FINAL Phase
INITIAL Phase	leads to	Charter — Scope Statement
INTERMEDIATE Phase	leads to	Plan / Baseline — Progress / Acceptance
FINAL Phase	leads to	Approval — Handover — Product

At each phase boundary, a management decision is made: proceed, modify, or terminate. These decision gates are what separate disciplined project management from hope-based management.

---

The Role of the Project Sponsor

A thread running through every phase is the relationship between the Project Manager and the Project Sponsor.

The sponsor is not a passive funder. They are the PM's link to executive authority, the escalation path for risks that exceed the PM's tolerance, and the ultimate accountable party for business benefits.

---

Planning and Control Formulae Across the Lifecycle

The lifecycle establishes when major management work occurs. Planning and control formulae provide evidence about how well that work is progressing. The supplied lifecycle notes introduce two practical toolsets.

PERT Three-Point Duration Estimate

During planning, an uncertain activity duration can be represented by an optimistic estimate, a most-likely estimate and a pessimistic estimate:

$$t_e = \frac{t_o + 4t_m + t_p}{6}$$

Here, $t_o$ is the optimistic duration, $t_m$ is the most-likely duration, $t_p$ is the pessimistic duration and $t_e$ is the weighted expected duration. This is an estimating technique—not a guarantee—and its quality depends on the evidence behind all three inputs.

Earned Value Signals During Implementation

During implementation, cost and schedule performance can be compared with the approved baseline:

$$CV = EV - AC$$

$$SV = EV - PV$$

Cost variance ($CV$) compares earned value ($EV$) with actual cost ($AC$). Schedule variance ($SV$) compares earned value with planned value ($PV$). A negative result indicates an adverse variance in the relevant dimension. These measures support investigation and corrective action; they do not replace judgement about scope, quality, risk or stakeholder outcomes.

Applying the Lifecycle in Technical and Regulated Environments

In heavy engineering, manufacturing, infrastructure and defence delivery, lifecycle governance is commonly made visible through design reviews, approval gates, contractual milestones, acceptance evidence and controlled handover. The supplied notes emphasise three practical consequences:

• planning outputs may include subsidiary risk, configuration, quality, procurement and communication plans;
• phase-gate decisions should confirm that exit criteria and evidence are satisfied before major commitments are released; and
• closure may require acceptance testing, configuration verification, contractual close-out and transfer to the operational owner.

These examples illustrate common practice rather than universal contractual requirements. The applicable contract, organisational method and regulatory environment determine the actual gates and evidence required.

Project Contexts

The lifecycle model is universal, but its application varies depending on the nature of the project. There are four fundamental project types:

Each type follows the same four-phase lifecycle, but the emphasis within each phase shifts. Manufacturing projects, for example, typically have heavier Phase 2 planning requirements (engineering drawings, BOM development, procurement lead times) while service projects may have more complex stakeholder management in Phase 3.

---

Five Common Pitfalls

1. Skipping the charter. Jumping straight to planning without a signed charter means the PM has no formal authority and no agreed scope baseline.
2. Under-investing in planning. The pressure to "start doing" leads to inadequate plans, which leads to rework — the most expensive form of waste.
3. Ignoring the external environment. Stakeholder management, approvals, and community consultation are not optional extras. They can stop a project cold.
4. Treating close-out as paperwork. The handover phase is where organisational learning happens. Treat it as an investment, not a chore.
5. Failing to align with the Pareto window. If your project controls are concentrated in execution rather than design, you've already lost most of your cost-influence leverage.

---

Key Takeaways

• The project lifecycle has four phases: Starting, Organising & Preparing, Carrying Out the Work, and Closing.
• Each phase has defined deliverables that gate the transition to the next phase.
• The potential to add value is highest at the start; the cost of changes escalates toward the end.
• The Project Plan is the central control document — a living reference updated throughout the project.
• The Post-Implementation Review captures lessons learned and prevents institutional amnesia.
• The Project Sponsor is not a passive role — their active involvement is a critical success factor across all phases.