Understanding the Basics of Project Management: A Starter Kit for Your First Big Project
Plenty of organisations run their first big project without a project management office (PMO), dedicated project managers or a formal methodology. A new system, an office move, a restructure: someone capable gets handed it on top of their day job, and the hope is that goodwill fills the gaps.
It can work. But after more than 15 years delivering projects, from business improvement initiatives to multi-site technology programs, I've seen the same handful of basics make the difference between a project that lands and one that drifts. You don't need a heavy framework. You need a few simple tools, used consistently.
1. Name a sponsor and a project lead
Every project needs two named people: a sponsor who owns the outcome and makes the big calls, and a project lead who runs the work day to day. When nobody's quite sure who decides, decisions stall and issues bounce around.
Sponsor: Approves scope, budget and major changes, and removes roadblocks.
Project lead: Plans the work, tracks progress, raises risks and keeps everyone informed.
Team: Does the work and flags problems early.
2. Write a one-page project charter
Before work starts, get these on a single page and have the sponsor sign it off:
Why: The problem you're solving or the opportunity you're chasing.
What: What's in scope, and what's explicitly out.
When: The target finish date and two or three key milestones.
How much: The budget, including a contingency.
What done looks like: How you'll know the project has succeeded.
One page forces clarity. If it won't fit, the project probably isn't defined well enough to start.
3. Keep a simple RAID log
A RAID log tracks risks, assumptions, issues and dependencies. A spreadsheet is fine. For each entry, record what it is, how serious it is, who owns it and what's being done about it, and review it every week. Most project surprises were sitting in someone's head weeks earlier. The log gets them written down while there's still time to act.
4. Set a weekly rhythm
A short weekly check-in and a one-page status update do more for a project than any software. Answer the same three questions every week:
What did we finish?
What's coming next?
What's at risk, and what do we need from the sponsor?
Add a simple red, amber or green rating for schedule, budget and scope so the sponsor can see at a glance where attention is needed.
5. Control changes deliberately
Changes are normal. Unmanaged changes are what blow out budgets. Agree a simple rule: any change to scope, timing or cost gets written down, assessed for impact and approved by the sponsor before work starts on it.
6. Close the project properly
When the work is done, formally hand it over, check the success measures from your charter, and hold a short lessons-learned session. Those lessons are what make your next project easier.
When it's time to get help
These basics will carry a lot of projects. It's worth bringing in an experienced project manager when:
The project is large, high-risk or touches critical systems.
It's already behind schedule or over budget and nobody's sure why.
Several teams, vendors or sites need coordinating.
Your project lead doesn't have time to do it properly alongside their day job.
At Sigma Management Consultancy, I help organisations put this kind of practical structure in place, run independent project health checks, and lead projects that need a steady hand.
If your next project feels bigger than your team's capacity, get in touch and we'll talk through where to start.
Comments