This is lesson 1 of 10 in a project management basics course. It is written for someone running a delivery in a mid-sized company who wants a straight path from start to close. Each lesson has a clear concept, a worked example, a checklist, and links to guides already on this site.
All ten lessons follow the same illustrative example, labelled as such: a custom industrial test-bench delivery, with an approved budget of €120,000 and a planned duration of six months. The figures are sample amounts, not a real case and not a ControlRoom result. It is the same kind of delivery used in the project budget Excel template guide.
A project has an end and a result to deliver
Day-to-day work keeps going: a workshop builds, a laboratory tests, a design office updates drawings. A project exists for a different reason: a defined result has to be delivered to someone, within a boundary, and then the work has to close.
Three traits make it recognisable:
- there is an objective written so that, at the end, you can say whether it was met;
- there are constraints of time, cost and scope, often also of quality and of people;
- there is an end: acceptance, handover, or an explicit decision to stop.
If there is no end, you are not running a project: you are running a standing activity. The distinction is practical. It changes who decides, how progress is measured, and when you are allowed to say «we have delivered».
Objective, constraints, and what stays out
The objective says what must be achieved, not every task on the list. «Design, build, install and have a test bench accepted in the client’s laboratory» is an objective. «Do a good job on the test bench» is not: you cannot close it.
Constraints say within which limits that objective still holds. The three used most often are:
| Constraint | Question it answers | Why the project manager needs it |
|---|---|---|
| Scope | What is included, and what is not? | Stops the work from growing without a decision |
| Time | By when is it delivered? | Makes slips visible instead of silent |
| Cost | Against which approved budget? | Keeps actuals, commitments and forecast in one view |
Other constraints are often just as real: the expected quality (the acceptance protocol), the people available, access windows at the client, lead times on components. The job is not to defend one constraint and ignore the others. It is to show when one of them moves, and what that does to the rest, so a decision can be taken in time.
It is also worth writing down what stays out. If it is not written, someone will eventually treat it as included. In lesson 2 this becomes a short project charter: objective, scope, stakeholders and success criteria in one place.
What the project manager does
The project manager holds together the objective, the constraints, the people and the decisions. They do not design the bench instead of engineering, and they do not sign every purchase order instead of procurement. They make sure the work has a shared frame, that gaps are seen early, and that choices go back to the person who has the authority to make them.
On a delivery such as the example, that usually means the project manager:
- agrees the objective and the scope with the sponsor and the client, and updates them when they change;
- sets a reference plan and budget, and compares them with actual progress;
- coordinates internal roles and suppliers, without taking over technical accountability;
- brings facts to the review: what has been delivered, how much is already committed, which risks are open, which decision is needed;
- records change requests, so a casual «while you are there» does not become hidden scope.
This is easier when plan and costs live in the same place. You can start in ControlRoom Free; the guide ControlRoom Free: a guide to your first project walks through the first steps.
The minimum roles that make the work governable
A project manager cannot close a delivery alone. Even a small team needs a few clear accountabilities. Titles vary from company to company; what matters is that everyone can see who decides, who does the work and who accepts it.
| Role | What they do or decide | In the test-bench example |
|---|---|---|
| Internal sponsor | Approves the objective, the budget and changes of scope | The operations lead in the example company |
| Project manager | Holds together plan, costs, risks and day-to-day decisions | Single point of contact for the client and the team |
| Design / engineering | Defines the technical solution and stands behind it | Mechanics, electrical cabinet, test sequence |
| Purchasing | Orders, lead times, suppliers | Steelwork, motors, sensors |
| Workshop and installation | Build, install, commission | Installation in the client laboratory |
| Client technical counterpart | Accepts interim deliveries and the final test | The laboratory that will use the bench |
| Client quality (if involved) | Joins acceptance against the agreed protocol | Acceptance tests |
If two people think they decide the same thing, or if nobody can accept a delivery, the project stalls in practice even while tasks are moving. When roles overlap, the guide on how to create a technical team responsibility matrix goes one level deeper.
Illustrative example: the test-bench delivery
Illustrative example, not a real project. Picture a mid-sized mechanical company in Northern Italy that has to design, build and install a custom test bench in a client’s laboratory. The approved budget is €120,000 and the planned duration is six months. The figures are sample amounts and they stay the same in later lessons, and in the budget template guide.
An objective you can actually close reads like this:
Design, build, install and have a test bench accepted in the client’s laboratory within six months, against an approved budget of €120,000, according to an agreed test protocol, and train two of the client’s technicians.
Constraints that are already visible at the start:
- Scope. In: mechanical and electrical design, the test sequence, build, installation, commissioning, training, as-built documentation. Out: civil works at the client, changes to the client’s production line, a multi-year maintenance contract.
- Time. Delivery and acceptance by the end of month six. The client laboratory is available only in the last three weeks. Some components have an eight-week lead time.
- Cost. Approved budget €120,000, already split by line (engineering, components, external laboratory, installation, project management, contingency).
Without this frame, the work is just «a test bench to get done». With it, the project manager already has three concrete conversations: the installation window, the long-lead components, and what stays outside scope if the client asks for an addition.
Mini-exercise and checklist
Take a piece of work you are running now, or use the test-bench example, and write on one page:
- The objective in one sentence, with a result that can be accepted.
- The delivery date and the reference budget (even if it is still provisional).
- Three items inside scope and three items outside it.
- The sponsor, the project manager, who does the technical work, and who accepts on the client side.
- The tightest constraint today: time, cost, scope, people, or access to the client.
Lesson 1 checklist:
- ☐ I can explain why this work is a project and when it ends.
- ☐ The objective is written so that delivery can be a yes or a no.
- ☐ Scope, time and cost are visible together, not in three separate conversations.
- ☐ What stays out is explicit.
- ☐ Sponsor, project manager, delivery roles and the client counterpart have names.
- ☐ I know which constraint deserves the next decision.
The next lesson
In lesson 2 these answers become a project charter: a short start-up document with scope, stakeholders and success criteria. That is the step that turns the test-bench example into a project you can govern, not just work that has started.
If you want to put objective and constraints into a workspace now, start with ControlRoom Free or begin from the downloadable resources. Later in the course we will also use the ten questions of a project review that decides.