What is a Project

The "Why": Why This Definition Matters More Than You Think

Every organisation runs hundreds of activities simultaneously — manufacturing runs, IT maintenance, customer service cycles, payroll processing. Most of these are operations: ongoing, repetitive, and designed to keep the lights on.

But occasionally, an organisation needs to do something new. Build a bridge. Launch a product. Relocate a facility. Implement a new ERP system. These are projects, and confusing them with operations is one of the fastest paths to wasted budgets, missed deadlines, and organisational frustration.

Understanding the precise nature of a project — and how it differs from the day-to-day work of an organisation — is the single most important conceptual foundation for anyone entering the field of project management. Get this wrong, and every tool, technique, and methodology you learn later will be applied to the wrong problem.

The "What": Defining a Project

PMBOK Definition: A project is a temporary endeavour undertaken to create a unique product, service, or result. — Project Management Body of Knowledge (PMBOK Guide), PMI

In practical terms, a project is a unique set of inter-related activities, with defined start and finish times, designed to achieve a common objective.

Two characteristics make a project fundamentally different from everything else an organisation does:

1. Temporary — A project has a definite beginning and a definite end. It does not run forever. The end is reached when the project's objectives have been achieved, when it becomes clear the objectives cannot be met, or when the need for the project no longer exists.

2. Unique — The product, service, or result produced by the project is different in some significant way from all similar products or services. Even if you've built ten warehouses before, the eleventh has a different site, different constraints, and different stakeholders.

Defining Project Management

PMBOK Definition: Project Management is the application of knowledge, skills, tools, and techniques to project activities to meet project requirements.

In practice, project management is the integration of project activities through the project life cycle to achieve the delivery of a defined product or service within prescribed constraints of time, budget, scope, and quality.

What is "Management by Projects"?

Some organisations take the concept further and adopt a Management by Projects philosophy. This is an organisational approach that uses projects as the primary vehicle for achieving strategic goals. Rather than managing business activities purely through functional departments, these organisations define their key initiatives as projects and manage them with project management discipline.

This approach incorporates ongoing operations but positions project delivery as the mechanism for organisational change and strategic advancement.

The "How": Separating Projects from Operations

The most practical skill you can develop early in your PM career is the ability to distinguish project work from operational work — because they require fundamentally different management approaches.

The Relationship Between Management Disciplines

Project management does not exist in isolation. It draws from — and overlaps with — two other core management disciplines:

General Management covers all aspects of the ongoing operations of the performing organisation — finance, HR, procurement, and corporate governance.

Technical Management covers the specialised technical knowledge required for a project's specific domain — whether that's civil engineering, software development, or pharmaceutical research.

Project Management sits at the intersection, integrating both general and technical management knowledge to achieve project-specific objectives.

Why Does Effective Project Management Matter?

When applied effectively, project management delivers measurable organisational value:

• Schedule adherence — projects are delivered on time
• Budget control — projects are delivered within financial constraints
• Quality improvement — deliverables meet or exceed stakeholder expectations
• Risk minimisation — threats are identified and mitigated proactively
• Productivity gains — resources are used efficiently, improving profitability

The "How" Applied: Key Roles in a Project

Best practice project management operates with a cross-organisational focus and three distinct but interdependent roles. Each must understand the others' responsibilities in relation to both project outcomes and corporate goals.

Project Sponsor

The sponsor is the owner of the project — the individual who supports, funds, and is accountable for the project's success. Their responsibilities include:

• Approving the project proposal and signing off the project brief
• Ensuring key business resources are available as planned
• Supporting the project manager in resolving risks and issues
• Approving all changes to scope, schedule, and budget
• Formally accepting the project's deliverables

Key Insight: The project sponsor is far and away the most important stakeholder. They are the primary risk-taker and are not a "silent partner" — they retain the right to make decisions. The wise project manager will keep them informed and engaged throughout.

Project Manager

The project manager is the integrator — the person responsible for planning, executing, and closing the project. Their responsibilities include:

• Producing the project brief and preliminary plan (with the sponsor)
• Developing the detailed project plan with team members and stakeholders
• Managing day-to-day project activity
• Providing motivation and direction to the project team
• Monitoring performance and updating the project schedule
• Managing risks, issues, and change requests
• Ensuring a Post Implementation Review is conducted

Project Team Member

Team members contribute technical expertise under the direction of the project manager. They work cooperatively with the team to meet the project's deliverables and may be internal or external to the organisation, including consultants and contractors.

The Pitfalls: Common Mistakes in Understanding Projects

Treating a project like an operation. Applying ongoing management approaches — fixed hierarchies, standing committees, unchanging processes — to a temporary, unique endeavour almost always leads to rigidity, scope creep, and missed deadlines.

Ignoring the "temporary" nature. Projects that never end aren't projects — they're undisciplined operations in disguise. If there's no defined end point, there's no accountability for delivery.

Underestimating uniqueness. Even "routine" projects (another office fit-out, another software release) have unique constraints, stakeholders, and risks. Assuming the last project's playbook will work identically this time is a recipe for failure.

Neglecting the sponsor relationship. The sponsor is not just a chequebook. Without active sponsor engagement — especially for resolving escalated risks and approving scope changes — the project manager fights with one hand tied behind their back.

Key Takeaways

• A project is temporary and unique — these two characteristics distinguish it from all other organisational activity.
• Project management integrates knowledge from general management and technical disciplines to deliver defined outcomes within constraints of time, budget, scope, and quality.
• Three key roles — sponsor, project manager, and team members — form the governance backbone of every project.
• Management by Projects is a strategic approach where organisations use projects as the primary vehicle for achieving business goals.
• Effective project management improves schedule adherence, budget control, quality, risk management, and productivity.