Project Management

Project management is the discipline of turning a temporary, one-off effort into a predictable outcome — on scope, on time and on budget — by planning the work and then actively steering it to completion.

Project management is the application of knowledge, skills, tools and techniques to project activities in order to meet the project’s requirements. Unlike operational work, which is ongoing and repetitive, a project is temporary: it has a defined start and end, a unique deliverable, and a finite set of resources. The project manager is accountable for balancing the competing demands of scope, schedule, cost, quality, resources and risk — often visualised as the "triple constraint" — while keeping stakeholders aligned and the team productive.

Why it matters

Without deliberate management, projects drift: scope expands unchecked, deadlines slip quietly, costs surprise everyone at the end, and no one is sure who owns what. Good project management makes the invisible visible. It creates a baseline to measure against, a rhythm of communication so problems surface early, and a single point of accountability. Organisations invest in project management because the alternative — improvised delivery — reliably costs more, takes longer and produces worse results.

When to use it

Use formal project management whenever an effort is temporary, cross-functional, and carries enough risk or cost that failure would hurt. A two-hour task does not need a charter; a six-month system migration across five departments absolutely does. The heavier the coordination, the more uncertainty, and the more money at stake, the more structure pays off. Small, well-understood work can use a lightweight approach; large, novel or regulated work needs the full toolkit.

How to use it

1. Initiate: define why the project exists, who sponsors it, and what success looks like — captured in a project charter.
2. Plan: break the work down (WBS), sequence it into a schedule, estimate cost, identify risks, and agree how you will communicate.
3. Execute: mobilise the team, produce the deliverables, and manage day-to-day coordination.
4. Monitor & control: compare actuals to the baseline, manage change requests, and correct course before small variances become crises.
5. Close: obtain acceptance, release resources, capture lessons learned, and hand over to operations.

Example

A company is launching a new e-commerce site. The project manager writes a charter naming the sponsor (VP of Digital) and the goal (go live before the holiday season). They build a WBS covering design, build, content, payments and testing; sequence it on a Gantt chart; and identify the top risk (payment-gateway integration). As work proceeds they track progress weekly, escalate a two-week slip in the payment work early enough to add a specialist, and close the project after a successful launch — recording that the gateway estimate was optimistic so the next project plans better.

Template

A basic project management starter pack includes: a project charter, a work breakdown structure, a schedule (Gantt), a RAID log (risks, assumptions, issues, dependencies), a RACI matrix, a communication plan and a weekly status report format.

Browse templates →

Tools

Related topics

FAQs

Alternatives

• Product management — continuous, outcome-owned rather than temporary and output-owned
• Operations management — for repeatable, ongoing work rather than one-off efforts
• Agile delivery — an iterative style of project management for high-uncertainty work