1.1 Projects vs Business as Usual (BAU)

1.1 Projects vs Business as Usual (BAU)

Core Definition (APM BoK7 glossary): A project is a unique, transient endeavour undertaken to bring about change and to achieve planned objectives.

Learn this wording verbatim. The PFQ syllabus command verb Define states: "Give the nature, scope or meaning. This must come from the APM Body of Knowledge 7th edition." Twenty-four of the fifty-nine assessment criteria are define/state criteria, so the exact BoK7 phrasing is worth more marks than any paraphrase.

Every organization must balance two fundamental types of activity to survive and thrive: executing day-to-day operations to sustain immediate cash flow and services, and executing targeted initiatives to transform, innovate, and adapt to changing environments. In the language of the Association for Project Management (APM), this distinction is framed as Business as Usual (BAU) versus Projects.

Understanding what distinguishes a project from routine business operations—and appreciating why specialized management practices are required—is the bedrock of the APM Project Fundamentals Qualification (PFQ).

---

Deconstructing the APM Definition of a Project

The APM Body of Knowledge (7th Edition) defines a project with precision. Four elements within this definition demand thorough examination:

1. Unique: Every project possesses distinctive elements. Even when delivering similar products—such as building housing units from identical blueprints or deploying commercial software across multiple business units—each project encounters a unique confluence of stakeholders, site conditions, regulatory landscapes, team dynamics, supply chains, and geographical constraints. Uniqueness introduces novelty, which in turn means standard operating procedures alone cannot guarantee success.
2. Transient: Projects have a definitive lifecycle. They are not perpetual. A project begins at a recognized initiation point (often triggered by an approved Business Case), moves through planned development and deployment phases, and culminates in a formal handover and closure. The project organization is temporary; teams assemble for the purpose of delivery and disband when the mandate is completed.
3. Brings About Change: A project is not undertaken to sustain the current state. BoK7 builds change into the definition itself: a project exists to move the organisation from where it is now to a different, better place. This is why the key purpose of project management is to effect beneficial change — the exact wording APM uses.
4. Planned Objectives: A project is initiated to deliver specific, pre-determined targets. These objectives are typically expressed in terms of technical deliverables (outputs), capabilities (outcomes), and quantifiable return on investment (benefits), governed by baseline constraints of scope, schedule, cost, and quality.

---

Differentiating Projects and Business as Usual (BAU)

Business as Usual (BAU)—also referred to as operations—comprises the ongoing, cyclical, and repeatable activities necessary to maintain an organization's continuous baseline performance. Examples include processing payroll, running customer support desks, manufacturing consumer goods on an assembly line, or conducting annual statutory audits.

While projects and operations both require human effort, planning, financial budgets, and resource coordination, they diverge fundamentally across five critical dimensions:

The Synergy Between Projects and Operations

Projects and BAU do not exist in opposition; they function as a symbiotic continuum. A successful business uses profits generated by steady-state operations to fund strategic projects. In turn, projects deliver new physical assets, updated software systems, or restructured business processes that are handed over into operations.

Once a project reaches handover, the temporary project team transfers operational responsibility to the permanent operational teams. The outputs of the project become the new standard operating environment for BAU, realizing long-term business benefits.

---

The Definition and Core Facets of Project Management

Because projects are transient, unique, and inherently uncertain, applying routine operational management methods to them invariably leads to cost overruns, missed deadlines, and unfulfilled expectations. This necessitates a distinct professional discipline.

Definition (APM BoK7 glossary): Project Management is the application of processes, methods, knowledge, skills and experience to achieve specific objectives for change.

Note the final three words. APM does not say "specific project objectives" — it says "specific objectives for change", and distractors in PFQ questions routinely swap that ending.

Let us break down each of these five critical elements:

• Processes: Structured sequences of activities that guide a project systematically through its life cycle, such as risk management workflows, configuration management, and formal change control.
• Methods: Standardized techniques, frameworks, and tools used to structure and execute project tasks (e.g., Work Breakdown Structures, Critical Path Scheduling, and Earned Value Management).
• Knowledge: Theoretical understanding and practical familiarity with project domains, industry regulations, technical standards, and governance principles.
• Skills: Practical interpersonal and managerial abilities, encompassing communication, stakeholder negotiation, leadership, conflict management, delegation, and problem-solving.
• Experience: Practical insight gained from delivering past projects, enabling the project professional to anticipate challenges, exercise sound judgment, and apply lessons learned.

---

The Primary Purpose of Project Management

The overarching purpose of project management extends far beyond simply completing a to-do list. In the APM framework, project management serves three primary purposes:

1. Effecting Beneficial Change

Organizations cannot remain static; they must adapt to technological disruption, regulatory mandates, and competitive pressures. Project management acts as the engine of organizational change. It takes abstract strategic concepts and converts them into tangible reality, bridging the chasm between corporate intent and operational capability.

2. Managing Trade-Offs (The Triple Constraint)

Every project operates within bounded constraints, traditionally known as the Time, Cost, and Quality triangle (or the Iron Triangle):

• Time (Schedule): The available duration and milestone deadlines.
• Cost (Budget): The financial and material resources allocated.
• Quality (Scope & Performance): The deliverables' fitness for purpose and adherence to technical specifications.

These constraints are interdependent. An alteration to one constraint inevitably impacts the others. For example, if executive leadership demands that a project deliver two months earlier than scheduled (Time reduction), the project manager must evaluate trade-offs: either increase funding to hire additional labor or expedite freight (Cost increase), or reduce the scope and non-essential features (Quality/Scope decrease).

A core duty of the project manager is to balance these trade-offs transparently, presenting objective impact assessments to the Project Sponsor so informed business decisions can be made.

3. Delivering Outputs to Realize Benefits

A technical output has no inherent value unless it enables a positive operational change. Project management provides the disciplined framework ensuring that technical deliverables (outputs) meet user requirements, allowing operational teams to adopt new ways of working (outcomes), which ultimately generate measurable improvements and return on investment (benefits).

Without structured project management, projects frequently suffer from scope creep, cost escalation, stakeholder disillusionment, and failure to realize the business case justification.