Project Management Basics

A project is temporary work with a clear finish line that creates something specific. Making dinner every night is routine. Hosting Thanksgiving for 20 is a project. The Project Management Institute (PMI) describes project management as applying knowledge, skills, tools and techniques to project activities to meet the project's requirements. In plain English: plan the work, then work the plan.

Write a SMART goal

The triple constraint

Every project balances three things: scope (what you'll deliver), time and cost. Change one and the others move. Want it sooner? You'll need more money or less scope. Quality sits in the middle and suffers when the three are out of balance.

Scope is the boundary of the project: what's in and what's out. Write it down. The most common way projects go wrong is scope creep: small “can we also...” requests that pile up until the deadline is impossible.

Break it down

Split the project into big chunks (deliverables), then split each chunk into tasks. Professionals call this a work breakdown structure (WBS). Keep going until each task is small enough that one person could do it in a day or a few days.

A good task has:

• A verb: “Print 50 flyers,” not “Flyers.”
• One owner: a single name, even if others help.
• A done-when: how you'll know it's finished.
• An estimate: how long it will take.

Estimates are usually too optimistic. Break big tasks into smaller ones (small estimates are more accurate), compare to how long similar work took before, and add a buffer.

Some tasks can happen at the same time. Others have to wait. A dependency means one task can't start until another finishes: you can't price items until you've sorted them. A milestone is a key checkpoint with zero length, like “all items priced.”

A Gantt chart shows each task as a bar across a calendar, so you can see what overlaps and what's waiting. Engineer Henry Gantt popularized it in the early 1910s, and it's still a standard tool.

The critical path is the longest chain of dependent tasks. It sets the shortest possible length of the whole project. If any critical task slips by a day, the finish date slips by a day. Tasks off the critical path have some wiggle room, called slack or float.

• Sponsor: the person who wants the result and approves money and big decisions. For a school fundraiser, maybe the band director.
• Project manager: keeps the plan, tracks progress, clears roadblocks, and communicates. Doesn't have to do every task.
• Team members: do the tasks.
• Stakeholders: anyone affected or interested: neighbors, parents, the school office.

RACI: clear up who's responsible

For each task, mark one role per person: Responsible (does it), Accountable (owns the result, only one person), Consulted (asked before), Informed (told after).

If everyone owns it, nobody owns it. Every task needs exactly one accountable person.

A kanban board shows work as cards moving through columns, usually To do → Doing → Done. It doesn't show dates. It shows flow: what's waiting, what's in progress, and where work is getting stuck. Teams often set a WIP limit (work in progress), a cap on how many cards can be in “Doing” at once, so people finish things before starting new ones.

Many people use both: a Gantt chart to plan the dates, and a kanban board to run the day-to-day.

Plan for what could go wrong

A risk is something that might happen and hurt the project. List them early in a simple risk register, score each one, and decide what you'll do.

The four classic responses: avoid it (change the plan), reduce it (make it less likely or less bad), transfer it (insurance, a contract), or accept it (and have a backup plan).

Write a status update people will read

Send updates on a regular schedule, keep them short, and lead with the overall status. Many teams use a traffic light: green (on track), yellow (at risk), red (off track, needs help).

Bad news early is good news. Flag problems the moment you see them, while there's still time to fix them. Surprises at the deadline are what people remember.