Module 1: Project Management Basics
What Makes a Project a Project
Before you can manage a project well, you need to know when you are actually dealing with one. Many people call every piece of work a "project", and then wonder why planning tools feel heavy for some tasks and too light for others. Learning to tell projects apart from routine operations helps you choose the right amount of planning, the right people and the right way to measure success.
The defining features of a project
A project is a temporary effort undertaken to create a unique product, service or result. Three features follow from that definition, and you should check for all of them:
- It is temporary. A project has a definite start and a definite end. The end comes when the objectives are met, when it becomes clear they cannot be met, or when the need for the project disappears. "Temporary" does not mean short; a road construction project can run for years, but it still ends.
- It produces something unique. The output is new in some way. Opening a second branch of a pharmacy is a project even though you have done it once before, because the location, landlord, staff and local conditions are different.
- It has a defined objective. There is a clear result the work is meant to deliver, usually expressed together with constraints of time, cost and quality.
Projects also tend to be progressively elaborated: you start with a broad idea and add detail as you learn more. And they usually involve a degree of uncertainty, because you are doing something you have not done in exactly this way before.
Projects versus operations
Operations are the ongoing, repetitive work that keeps an organisation running: processing payroll every month, serving customers at the counter, reconciling M-Pesa till statements each evening. Operations aim for consistency and efficiency. Projects aim to bring about change.
| Feature | Project | Operations |
|---|---|---|
| Duration | Temporary, with an end date | Ongoing |
| Output | Unique result | Repeated product or service |
| Goal | Deliver a change, then stop | Sustain the business |
| Team | Often assembled for the project | Usually a stable department |
| Main challenge | Managing uncertainty | Managing efficiency and quality |
The two are connected. Many projects exist to improve operations, and when a project finishes, its output is usually handed over to an operations team to run.
The triple constraint and beyond
Every project balances scope (what you will deliver), time (when) and cost (with how much money and effort). Quality sits in the middle, affected by all three. If one changes, at least one of the others is usually affected. Add features and you will need more time or money; cut the budget and you may have to reduce scope. Modern practice also pays attention to risk, resources, benefits and stakeholder satisfaction, but the triple constraint remains a useful first lens.
Worked example: is it a project?
Consider Wanjiru, operations manager at a hardware distributor in Nairobi. Her to-do list includes:
- Weekly stock count at the Industrial Area warehouse. Repetitive, ongoing, same method every week. This is operations.
- Move the warehouse from Industrial Area to a new site in Athi River by the end of March. Temporary, unique (new site, new layout, new transport routes), clear objective and deadline. This is a project.
- Answer customer calls about delivery times. Ongoing service. Operations.
- Introduce a barcode scanning system for stock receiving. A one-time change with a defined result and budget. A project, which, once complete, will change how the weekly stock count (an operation) is done.
Wanjiru now knows that items 2 and 4 deserve a written objective, a plan, a budget, a named sponsor and an end date. Items 1 and 3 need good procedures, not project plans.
Common mistakes to avoid
- Treating a project as "just more work". Without an end date and objective, a project drifts on for months and competes with daily tasks it always loses to.
- Over-managing routine tasks. Writing a charter for a weekly report wastes effort. Match the formality to the work.
- Vague objectives. "Improve the warehouse" is not a project objective. "Relocate all stock to Athi River with no more than two days of interrupted deliveries" is.
- Forgetting the handover. Because projects end, you must plan who will own and operate the result afterwards.
Once you can recognise a project, everything else in this course, from lifecycles to schedules, has a clear place to attach to.
Exercise
List eight pieces of work you or your organisation are doing this month. For each, mark whether it is a project or operations and write one sentence explaining why, using the three features: temporary, unique and defined objective. For each item you marked as a project, write a one-line objective that includes a measurable result and an end date.
Key points
- A project is temporary, produces a unique result and has a defined objective.
- Operations are ongoing and repetitive; projects create change and then end.
- Scope, time and cost are linked: changing one usually affects the others and quality.
- Match the level of planning to the work, and plan the handover to operations.