Project basics: projects vs operations and programs, the triple constraint, and project roles (sponsor, project manager, PMO, team, stakeholders)

A project is a temporary effort with a defined start and end that creates a unique product, service or result. Moving a company's email to a cloud service, building a new branch office network or rolling out a new ticketing tool are projects. Running the help desk every day, patching servers each month and answering password-reset calls are operations: they are ongoing and repetitive, and they keep the business running. Temporary does not mean short; it means the effort ends when its objectives are met, or when it is clear they cannot or should not be met. Projects often end by handing something over to operations, which is why the two groups need to work together from the start.

Projects can be grouped. A program is a set of related projects managed together because coordinating them brings benefits you would not get managing them separately, for example a digital workplace program with separate projects for laptops, collaboration tools and training. The program manager watches the dependencies between those projects and the combined benefit. A portfolio is the collection of all projects, programs and even some operational work an organization is funding, chosen and balanced to meet its strategy. Portfolio managers decide which efforts get money at all; project managers deliver the efforts that were chosen.

Every project is shaped by the triple constraint: scope (what will be delivered), time (the schedule) and cost (the budget). Quality sits in the middle, and many modern texts add risk and resources as further constraints. The key idea is that the constraints are linked. If the sponsor adds scope, time or cost must usually grow, or quality suffers. If the budget is cut, scope or quality usually shrinks. When an exam question describes a change to one constraint, ask what happens to the others, and remember that the project manager's job is to show those trade-offs to the people who decide, not to absorb them silently.

The Project+ exam expects you to know who does what. The sponsor champions the project, provides or secures funding, approves the charter and major changes, and helps remove organizational obstacles the project manager cannot move alone. The project manager plans, coordinates and controls the work day to day and is accountable for delivering the agreed objectives. The project management office (PMO) sets standards, templates, methods and governance for projects across the organization and may provide coaching, tools or portfolio reporting. The project team does the work, often including subject matter experts (SMEs) who bring specialist knowledge. Stakeholders are anyone affected by or able to influence the project: users, customers, department heads, vendors, regulators.

A few supporting roles also appear on the exam. A project coordinator or project scheduler supports the project manager with documentation, meeting logistics, schedule updates and status tracking, but usually has less decision authority. A product owner, on agile projects, owns the backlog and represents the customer. A functional manager (the line manager of a department) owns people and may lend them to the project. Knowing whose authority applies is often the whole question: the sponsor approves funding, the functional manager releases staff, the project manager directs project work.

Consider a worked example. A regional hospital wants to replace its nurse call system. The chief nursing officer, who asked for it and controls the budget, is the sponsor and signs the charter. The PMO provides the charter template and requires monthly status reports in its standard format. A project manager from IT is assigned; a coordinator keeps the schedule and minutes. The team includes network engineers, the vendor's installers and two nurses acting as SMEs. Stakeholders include every ward manager, the facilities team, the service desk and the patients who press the buttons. When the vendor quotes more rooms than planned, the project manager shows the sponsor the options: more money, more time, or fewer rooms in phase one.

Common mistakes: calling a monthly patch cycle a project (it repeats forever, so it is operations); treating a program as just a big project rather than a group of related projects; assuming the project manager approves the budget or the charter (the sponsor does); and thinking the PMO manages each project directly. Another frequent error is treating stakeholders as only the people in meetings. The service desk that will support the result and the users who will change how they work are stakeholders even if they never attend.

Exam questions are usually written as short scenarios. 'Ongoing, repetitive work' points to operations; 'temporary, unique result' points to a project; 'several related projects coordinated for combined benefit' is a program; 'selected to meet strategic goals' is a portfolio. 'Who provides funding and signs the charter' is the sponsor. 'Who sets templates and standards across projects' is the PMO. 'The customer wants more features but the date is fixed' is a triple constraint question: the answer involves more cost, reduced quality or a formal trade-off decision.

Key terms

Project

A temporary endeavor with a defined beginning and end that creates a unique product, service or result.

Operations

Ongoing, repetitive work that keeps the business running, such as help desk support and routine patching.

Program

A group of related projects managed in a coordinated way to obtain benefits not available from managing them separately.

Portfolio

All the projects, programs and related work an organization funds, selected and balanced to meet strategic goals.

Triple constraint

The linked limits of scope, time and cost, with quality at the center, where changing one affects the others.

Sponsor

The senior person who champions the project, provides funding, signs the charter and approves major changes.

Project management office (PMO)

The group that sets project standards, templates and governance across the organization.

Check yourself