Project Management for Small Business — Without PMP

First, a warning that may save you the price of this course: **if your problem is that you

do not hold a PMP certificate, you are in the wrong place, and you most likely do not need one.**

About certifications

PMP was designed for people running large projects inside large organisations, with dedicated

teams, project management offices and written budgets. In this region it costs hundreds of dollars,

and its method assumes roles and documents that do not exist in a twenty-person company.

If you want it for the job market — because a posting asks for it — that is a legitimate

reason, and you should go and get it. This course will not give it to you and does not pretend to.

But if you want it because your projects run late and over budget, the certificate will not fix

that. What fixes it is far smaller and much closer to hand.

Projects versus operations

A basic confusion that causes half the chaos:

A project has a beginning, an end and a defined result. Operations repeat without end.

Delivering an online store to a client is a project. Answering support requests is operations.

Setting up a new branch is a project. Daily selling in that branch is operations.

Why does it matter? Because the tools differ. A project needs a plan, a scope and a date.

Operations need a procedure, a queue and a metric. Manage operations as a project and you exhaust

your team with plans that never end. Manage a project as operations and it never arrives.

The first thing to do after this lesson: separate your two lists.

Where your projects actually slip

In small companies, delay is rarely caused by poor planning. The four real causes:

1. Nobody agreed what "done" means. The team says it is ready, you say something is missing.

Neither lied — the definition was never written.

2. A stuck decision. Work is waiting on an answer from you or a client, nobody counts those

days as delay, and they surface all at once at the end.

3. One person on three projects. It looks like they are working on all three; in fact they are

delaying all three. Context switching consumes time that appears on no schedule.

4. Uncounted change. A "small addition" happens ten times, and not one of them was recorded

with a time and a cost.

Notice that all four are managerial, not technical, and all four are solved by decisions rather

than tools.

What the real minimum is

You need no software, no methodology and no project office. You need five things, written down:

1. One clear result for the project
2. One decision owner, by name
3. A task list where every task has an owner and a date
4. A written definition of "done"
5. A short, fixed weekly meeting

Five. Anything you add on top of them has to justify itself.

Methodologies: which one do you pick?

A question that comes up often, and my answer is that it is a premature one. But so you know the map:

Waterfall — plan everything first, then execute in order. Suits projects whose **result you know

precisely from the start**: setting up a branch, installing accounting software, obtaining a

certification.

Agile / Scrum — work in short batches and review after each one. Suits what **you discover as you

go**: a new product, a site whose shape has not settled, a marketing campaign learning from its own

results.

Mixed — which is what actually happens in most small companies: a general plan for the whole

project, and a fortnightly review that adjusts what comes next.

The practical rule: **if you know the result precisely, plan. If you are discovering it, work in

batches.** And do not adopt a methodology by its name and vocabulary inside a twenty-person company —

adopt what solves your problem and leave the labels.

The cost of not managing

Before deciding this is all "extra work," add up roughly:

• A project a month late: what did the lost time cost you?
• A feature built and then found not to be what was wanted: how many days of work?
• Two employees waiting a week on a decision: how many days stopped?
• A client who left because delivery slipped: what was the contract worth?

These are not theoretical numbers — they are your own, from your last project. Total them, and compare

against the one hour a week this course asks of you. The gap is usually large enough to end the

argument.

What this course teaches

The next seven lessons build those five one at a time, along with what surrounds them: estimation,

dependencies, risk and closing. And its output is not a theoretical certificate — it is **a plan

for a real project of yours**, ready to run.

Action steps

Write two separate lists today: what is a project for you, and what is operations. Then pick **one

project** that will accompany you through every lesson of this course. Pick a real one that is

already running — not a hypothetical example.