A project is a temporary effort to create a unique product, service or result. It has a start, an end and a defined goal — unlike operations, which run continuously. Project management is the discipline of applying knowledge, skills, tools and techniques to deliver that goal: planning the work, organising people and resources, tracking progress and steering when reality diverges from the plan.
Launching a website, building a bridge, moving an office, running a marketing campaign and implementing new software are all projects. Answering support tickets or running payroll every month is operations — although improving the support process would be a project.
The triple constraint (and why it is really a quadruple)
Every project balances three competing constraints:
- Scope — what will be delivered.
- Time — when it will be delivered.
- Cost — the budget and resources available.
Change one and at least one other moves. Add scope without adding time or money and something gives — usually quality, which is why many practitioners place quality at the centre of the triangle. A useful way to start any project conversation is to ask the sponsor: "If we can only protect one of scope, time or cost, which is it?" The answer tells you how to make trade-offs for the rest of the project.
The five process groups
Most project management frameworks describe the work of managing a project in five groups of activities. They are not strictly sequential — monitoring runs throughout — but they give a useful mental model:
- Initiating — define the goal, identify stakeholders, get authorisation. Output: a project charter.
- Planning — break down the work, estimate it, sequence it, budget it, plan for risk and communication. Output: a project management plan with a WBS and schedule.
- Executing — do the work, lead the team, manage suppliers and communicate.
- Monitoring and controlling — compare progress to the plan, manage changes, track risks and issues, report status.
- Closing — hand over deliverables, release resources, capture lessons learned and formally close contracts.
What does a project manager actually do?
The job description says "plan, execute and close projects". In practice, a typical week looks like this:
- Clarifying — turning a vague request into a goal with success criteria everyone agrees on.
- Planning and re-planning — maintaining the schedule, budget and backlog as things change.
- Removing blockers — chasing decisions, escalating issues, negotiating for resources.
- Communicating — status updates, steering meetings, one-to-ones with key stakeholders.
- Managing risk — spotting problems early, while they are still cheap to fix.
- Leading people — often without formal authority over them.
Studies of project managers' time consistently find that communication dominates the role. Technical knowledge of the domain helps, but the ability to create clarity and keep people aligned is what separates good PMs from great ones.
Key roles on a project
| Role | Responsibility |
|---|---|
| Sponsor | Owns the business case, provides funding, makes the big decisions and removes organisational obstacles. |
| Project manager | Accountable for delivering the project's objectives within its constraints. |
| Project team | The people who do the work: designers, engineers, analysts, trades, writers. |
| Stakeholders | Anyone affected by or able to influence the project — users, customers, regulators, other departments. |
| Product owner (agile) | Owns the backlog and decides what gets built next to maximise value. |
| PMO | Project management office: sets standards, supports PMs and reports across a portfolio. |
Methodologies: predictive, adaptive and hybrid
Predictive approaches (often called Waterfall) plan the whole project up front and execute it in phases. They suit work where requirements are stable and changes are expensive, such as construction.
Adaptive approaches (Agile, including Scrum and Kanban) deliver in small increments and adjust based on feedback. They suit work with uncertain requirements, such as software and product development.
Hybrid approaches combine both — for example, a fixed milestone plan for governance with agile delivery inside each phase. Not sure which fits? Take the 2-minute methodology quiz.
Essential project management skills
- Scoping and planning — work breakdown, estimating, scheduling (Gantt charts, critical path).
- Risk management — identifying and responding to uncertainty (risk matrix).
- Financial control — budgeting and tracking (earned value).
- Stakeholder management — mapping influence and tailoring communication (stakeholder map).
- Leadership and negotiation — motivating a team and resolving conflict.
- Tool fluency — knowing at least one PM platform well. See our software guide.
Why projects fail
Post-mortems across industries point to the same handful of causes: unclear objectives, changing scope with no change control, unrealistic estimates, weak sponsorship, poor communication and risks that were known but not managed. Almost none of these are technical. The good news is that each has a well-understood countermeasure — a clear charter, a change process, three-point estimates, an engaged sponsor, a communication plan and a living risk register.
Where to go next
Read about the project life cycle, browse the glossary, or explore certifications if you want to formalise your skills.
Put this into practice
Use our free tools to apply what you just read — or get a free consultation if you want an expert to look at your project.