Projects, Operations, Programs and Portfolios

Start with the change and the endpoint

Before opening a task schedule, ask whether the work creates a defined result and hands it over or sustains an ongoing service. A project has distinctive, defined outputs, acceptance criteria and a limited timescale, whereas operations sustain service delivery. Temporary describes the organized project effort, not the lifetime of its output. A service-centre project can finish while the centre operates for years. A project may also be closed early following a justified termination decision; having an endpoint does not mean every project will achieve all its objectives. Distinctiveness concerns the output and its context; inventing a previously unknown technology is not required.

Not every task is a separate project

In the case, emailing a supplier is not a separate project; it is an activity within larger work. Relocating a branch may justify a separate project with different acceptance arrangements, responsibilities and risks. A useful working test is: What output will be accepted? Who will accept it? Where does the team’s assignment end? An inability to answer may indicate an idea requiring definition rather than a project ready for delivery.

Budget size is not the deciding test. Preparing a particular event can be a small project while running a large service remains operations. Recurrence is also inconclusive: each annual event can be managed as a project when it has a defined delivery, team and endpoint. Processing event registrations throughout the year may remain an ongoing operation. Classification concerns the work unit and its boundaries, not its importance.

From a project to a program and portfolio

A program coordinates related projects and operational work for beneficial change. Extend the fictional case: the network commissions a booking-system project and a separate reception-redesign project, each with its own assignment and acceptance, and links them with staff readiness and adoption of new procedures. Coordinating these components for improved service illustrates a program because the benefit depends on their combined operation. Including training and testing within one system-project assignment does not by itself make it a program. Coordination adds value by managing interdependence between components, not by counting activities.

A portfolio concerns selecting, prioritizing and controlling projects and programs in line with strategy and delivery capacity. When the network compares booking technology, a new branch and equipment renewal, it asks a portfolio question: Which work should receive resources first? The components need not produce one shared output; they are brought together for investment and organizational decisions.

Connecting delivery with operations

Try defining the endpoint: “The assignment ends when management accepts the system in the three branches against agreed tests and the operations owner accepts the operating instructions and support responsibility.” This is a learning example, not a contract template. It avoids making the project team indefinitely responsible for daily service. It does not establish that shorter waiting times have already been achieved; the next lesson separates outputs from benefits.