What is project management?
Project management is the practice of planning, coordinating and controlling temporary work so that a defined outcome is delivered within agreed limits of scope, time, cost and quality. Below: a precise definition, three worked examples, the vocabulary you will hear on day one, and a five-phase checklist you can run on your own project this week.
The definition, unpacked
- A project is temporary work with a defined start, end and outcome — unlike operations, which run indefinitely.
- Project management is the discipline of turning an intent into a delivered outcome inside agreed constraints of scope, time, cost and quality.
- The job is decision-making under uncertainty: sequencing work, allocating people and money, surfacing risk early and keeping stakeholders aligned.
- Method (predictive, agile or hybrid) is a choice you make per project; the underlying responsibilities do not change.
The simplest test: if the work has an end date and a deliverable, it is a project. If it repeats forever and is measured on throughput, it is operations — and it needs process management, not project management.
The five-phase process checklist
Every project passes through these five phases. Predictive projects walk them in order; agile teams cycle through them repeatedly at a smaller scale. The output column is what proves the phase actually happened.
- 1
1. Initiate
Prove the work is worth doing and get authority to spend.
- Write the problem statement and the measurable outcome, not the solution
- Name the sponsor and the decision-makers
- Estimate a rough order-of-magnitude cost and duration
- Get the charter signed before staffing the team
Output: Signed project charter with objectives, scope boundaries and success measures
Project charter template - 2
2. Plan
Turn the outcome into a sequence of work someone can actually execute.
- Decompose scope into a work breakdown structure down to assignable work packages
- Sequence dependencies, estimate durations and identify the critical path
- Set the cost and schedule baseline you will report against
- Log risks with owners and responses, and map who decides what
Output: Baselined schedule, budget, RACI and risk log
RACI matrix template - 3
3. Execute
Get the work done without the plan quietly drifting.
- Run a short, decision-focused delivery cadence
- Unblock the team — escalation is a service, not an admission of failure
- Keep the RAID log current so issues have owners and dates
- Protect quality: define done before work starts
Output: Working deliverables plus a current RAID log
RAID log template - 4
4. Monitor & control
Compare reality with the baseline and act on the variance.
- Report variance against baseline, not against last week's optimism
- Re-run the critical path when durations change — float is not a buffer you can spend twice
- Route every scope change through change control with a cost and date impact
- Escalate with options and a recommendation, never with a problem alone
Output: Weekly status report and approved change decisions
Status report template - 5
5. Close
Hand over cleanly and capture what the organisation learned.
- Confirm acceptance against the original success measures
- Transition ownership, documentation and support arrangements
- Run a blameless lessons-learned session and publish the actions
- Release the team and close the budget formally
Output: Acceptance sign-off and published lessons learned
Lessons learned template
Three worked examples
Example 1 — Office relocation (predictive)
Fixed date, fixed scope, hard external dependencies
The lease ends on 31 March, so the finish date cannot move. The manager builds a work breakdown structure covering fit-out, IT cabling, furniture delivery and staff moves, then sequences them. Cabling cannot start before the fit-out inspection passes, and furniture has a six-week lead time — that chain becomes the critical path. Weekly reporting tracks those tasks; everything else has float and gets less attention.
Takeaway: When the date is fixed, plan in detail and manage the dependency chain relentlessly.
Example 2 — Mobile app feature (agile)
Fixed team and cadence, negotiable scope
The outcome is 'reduce checkout abandonment'. Scope is a prioritised backlog rather than a signed spec. The team works in two-week sprints, ships a usable increment each sprint, and measures abandonment after each release. The manager protects the cadence, keeps the backlog ordered by value, and reports outcome metrics instead of percentage complete.
Takeaway: When the outcome is clear but the solution is not, fix the time and flex the scope.
Example 3 — Regulatory compliance programme (hybrid)
Immovable deadline, discovery-heavy delivery
The regulator's deadline is non-negotiable, so gates, budget and audit evidence are planned up front. The software changes underneath are built iteratively because the requirements are still being interpreted. Governance is predictive; delivery is adaptive. The manager reports gate readiness to the steering group and flow metrics to the team.
Takeaway: Hybrid is not indecision — it is choosing the right control per layer of the work.
Key terms in plain English
| Term | What it means |
|---|---|
| Scope | Everything the project will deliver — and explicitly what it will not. |
| Baseline | The approved schedule, cost and scope you measure progress against. |
| Critical path | The longest chain of dependent tasks; it sets the shortest possible finish date. |
| Float (slack) | How long a task can slip before it delays something else, or the project. |
| Milestone | A zero-duration marker for a meaningful event, like a gate approval. |
| Deliverable | A tangible output someone accepts — a document, a release, a building. |
| Stakeholder | Anyone who affects the project or is affected by it. |
| Risk vs issue | A risk might happen; an issue already has. Both need an owner. |
| Change control | The process that prices and approves scope changes before work starts. |
| Sprint | A fixed short cycle (usually 1–4 weeks) producing a usable increment. |
| Backlog | An ordered list of work not yet done, refined continuously. |
| Earned value | A method comparing planned, earned and actual cost to forecast the finish. |
Who does what
Sponsor
Funds the work, owns the business case, breaks organisational deadlocks.
Project manager
Plan, schedule, budget, risk, communication and the delivery decision trail.
Product owner
Priority order of the backlog and acceptance of increments (agile contexts).
Delivery team
Estimating their own work, building it, and calling out blockers early.
Steering group
Gate approvals, change decisions above the manager's tolerance.
Wondering how these roles progress? See the project manager career path or compare PMI certifications.
Frequently asked questions
- What is project management in simple terms?
- It is the practice of planning, coordinating and controlling temporary work so a defined outcome is delivered within agreed scope, time, cost and quality limits.
- What are the five phases of project management?
- Initiating, planning, executing, monitoring and controlling, and closing. Agile teams still perform all five, just in shorter overlapping cycles rather than sequential stages.
- What does a project manager actually do all day?
- Sequencing and re-sequencing work, removing blockers, forecasting the finish date and cost, surfacing risks before they become issues, and keeping stakeholders making decisions on time.
- Do I need a certification to be a project manager?
- No, but credentials such as CAPM or PMP shorten the credibility gap in hiring and are often required for senior or public-sector roles. Evidence of delivered projects matters more than the certificate alone.
- Is agile a type of project management?
- Agile is a set of delivery approaches, not a replacement for project management. You still need funding, scope boundaries, risk management and stakeholder governance around an agile team.
Where to go next
- The Project Lifecycle, End to End
Each phase in depth with the artifacts that prove it.
- Predictive vs Adaptive Delivery
How to choose a method for your project.
- Scope and the Work Breakdown Structure
Turning an outcome into assignable work.
- The Critical Path, Properly Explained
Why the longest chain sets your finish date.
- Risk Management as a Working Practice
Logging risks people actually act on.
- Stakeholder Management Without the Jargon
Mapping influence and keeping decisions moving.