Do your projects run you, instead of the other way around? (Part 1)

When people hear “project management,” they often think about Gantt charts, endless meetings, or a manager with a clipboard. And yes, some of that exists. But underneath all of it, there’s something much simpler: a method is just an agreement about how work moves from an idea to something real.

Think of it like this: you can be brilliant at what you do, deliver beautiful work, and still finish every week exhausted and behind. That usually happens because everything lives in your head. Every decision is made fresh. Every priority is renegotiated at 9am on a Monday. It’s like cooking a five-course dinner while inventing the menu between each plate.

That’s where a method comes in. It takes those decisions out of your head and puts them somewhere visible. That’s the whole trick. In this first part, let’s make the whole landscape readable. In part two, we’ll turn it into a routine you can start this week.

The two big families

Every method you’ll ever hear about belongs to one of two families. Once you see this, everything else falls into place.

Waterfall plans everything up front, then moves through phases in order: specification, design, build, test, deliver. Each phase closes before the next one opens. It gets a bad reputation in tech circles, and that’s unfair. Waterfall shines when the scope is genuinely fixed and change is expensive: a building, a regulated product, a client contract with a locked deliverable and a locked price.

Agile is the opposite bet. It assumes you’ll understand the problem better after you’ve built something than before. So you deliver in small, usable slices, show them to real people, and let what you learn reshape what comes next. Agile is a mindset rather than a rulebook — the rules come from the frameworks built on top of it.

The frameworks you’ll actually meet

● Scrum gives Agile a heartbeat. Work happens in fixed cycles called sprints, usually one or two weeks, and each one ends with something you can show. Around that rhythm sit three roles and a few recurring meetings — planning, a daily sync, a review, and a retrospective.

● Kanban came out of Toyota’s factories and it’s beautifully light. Columns, cards, and one rule: a maximum number of cards allowed in “Doing” at any moment. That single limit forces you to finish things instead of starting them.

● Lean asks one question about every activity: does the client feel this? Everything else is waste — waiting, rework, half-finished features, meetings that produce nothing.

● PRINCE2 (7th edition, 2023) and PMBOK (7th edition, now principles-based) are governance frameworks rather than daily working methods. You’ll meet them in large companies and public sector work.

The secret almost no article tells you

The pure approaches are rare. Most working teams run a hybrid. A typical freelance project looks like Waterfall on the outside — a signed scope, a fixed budget, a delivery date — and Agile on the inside, where you build in weekly slices and show progress as you go. That combination gives the client the certainty they need and gives you the flexibility you need.

So the goal is never to pick the “correct” method. The goal is to understand the pieces well enough to borrow the ones that solve your actual problem. That’s what we’ve just done.

Knowing the map is the easy half. Walking it is the other half — and that’s exactly what part two is about: how to start using all of this this week, whether you freelance or work inside a tech team.