OUR DISCIPLINES
Project & programme management in South Africa.
Every project that lands on time ran on decisions someone made early and held to. This is how project and programme management really works in South Africa: the roles, the market and what it takes to get it right, whether you’re hiring or building your own career.
A LOOK AT THE MARKET
The project and programme management market in South Africa.
Project and programme management qualifications have never been easier to come by, yet good delivery has never been harder to find. There are PMP holders, Prince2 practitioners and walls of Agile badges everywhere you look. What’s genuinely thin on the ground is the person who can walk into a programme that’s already behind, work out which problems will quietly sort themselves out and which is about to sink the whole thing.
That gap costs real money here, because of the kind of work South African businesses are running. Core banking replacements, network rollouts, mining and public-sector programmes, the sort of thing that runs for years and bleeds budget every month it slips. On these, a certificate tells you someone has passed an exam but it tells you nothing about whether they’ll hold their nerve when a product owner changes direction, two suppliers start blaming each other, and the deadline hasn’t moved.
Agile was supposed to be the answer to all this, and in the right hands it genuinely is, but it also filled the market with people who can run a stand-up and not much more. What they’ve worked out is that the ceremony and the tooling is the easy part, the hard part is holding scope when everyone’s pushing to add more, raising bad news early instead of burying it until the deadline, and keeping a room full of people with their own agendas moving toward the same result.
Which is why, when you strip it back, this whole market runs on one question: can this person actually be trusted to land the thing, or only to tell you how it’s going? The people who can genuinely deliver are rare, and they know it.
THE TITLE
What 'project manager' in a job title actually means.
The clearest way to read this title is to ignore it and ask one thing instead: if this person walked out tomorrow, how much of the outcome walks out with them? That single question tells you more than any label, because it measures the thing that actually varies from one “project manager” to the next, how much of the delivery genuinely lives in their head and their hands.
For some, the honest answer is not much. The plan exists, the decisions are made elsewhere, and their job is to keep it neat and moving, which is useful, but the project would survive them. For others, they are the reason it holds together at all. They’re the one seeing round corners, absorbing the chaos before it reaches the team, making the judgement calls that never make it into a status report. Take them out and the whole thing wobbles. Two people can carry the same title and sit at opposite ends of that spectrum, and the difference almost never shows up on a CV, because a CV records what someone was present for, not what would have failed without them.
This is what makes the title so easy to get wrong, and so worth getting right. When you’re hiring, the real task isn’t matching a title to a title, it’s working out how much of your outcome you’re about to make depend on one person, and whether this is someone who can carry that. And when you’re the one moving, it’s worth being honest with yourself about which end you’re operating at, because that, far more than the words on your business card, is what decides where you can go next and what you’re genuinely worth.
THE ROLES
The roles, and what each one involves.
Forget the job titles for a second. What really separates these roles is how much of the outcome each one carries, and how much room they have to make the call when things move and change constantly. Here is a view of the roles you’ll likely come across most, no matter the sector you’re in or hiring for.
Agile coach
Helps teams and sometimes whole organisations get better at how they deliver, rather than running any single project themselves. Works through influence, not authority, which makes it a role where real credibility matters more than the title. Most valuable where a business has adopted agile in name but not in practice.
Common requirements: deep delivery experience, coaching and facilitation, and the standing to challenge senior people without a mandate to.
Business analyst
Sits between the business and the people building the solution, turning vague needs into something a team can actually deliver against. Owns clarity, and often catches the expensive misunderstanding before it is built. Undervalued until a project ships the wrong thing.
Common requirements: requirements gathering, process mapping, stakeholder interviews, and enough technical fluency to be taken seriously by both sides.
Delivery manager
Focuses on how work gets from committed to done, clearing blockers and keeping the flow steady across one or more teams. Less about the plan on paper, more about whether things actually ship. Often the role that holds agile delivery together in practice.
Common requirements: flow and dependency management, team facilitation, and a practical read on what is really slowing delivery down.
PMO analyst or manager
Owns the reporting, governance and standards that let leadership see across a portfolio and trust what they are seeing. A behind-the-scenes role that matters most in large or regulated environments where consistency and audit are not optional.
Common requirements: portfolio reporting, governance frameworks, planning tooling, and the discipline to hold a standard when delivery teams push back.
Product owner
Decides what gets built and in what order, and is accountable for whether the output is actually worth having. Sits closest to value of any role here, and the good ones are ruthless about saying no. Frequently confused with a project manager, and it is not the same job.
Common requirements: prioritisation, backlog ownership, stakeholder management, and the judgement to defend a decision the business will live with.
Programme manager
Holds several related projects and the tangle between them, making trade-offs across the whole when they compete for the same people, money and time. A senior role measured by outcomes rather than activity, and the one that matters most when the stakes are high and political.
Common requirements: multi-project delivery, budget and risk ownership, executive stakeholder management, and the nerve to make unpopular calls.
Project manager
Takes a defined piece of work and is accountable for landing it on time, on budget and to scope. The backbone role of delivery, and the one where the gap between competent and genuinely trusted is widest. Judged on what lands, not on how busy the plan looks.
Common requirements: planning and scheduling, budget and risk management, stakeholder communication, and the judgement to surface bad news early.
Scrum master
Owns how a single team works rather than what it commits to, removing impediments and protecting focus. Lives or dies by whether the team ships more smoothly because they are there. The role most flooded with people holding a certificate and little real delivery behind it.
Common requirements: a recognised Scrum certification, real agile facilitation experience, and the read to tell a genuine blocker from noise.
Other disciplines we recruit in
Software engineering · Data and Analytics · DevOps and Cloud Engineering
IF YOU'RE HIRING
Hiring someone you can trust to get the job done.
The hardest part of a delivery hire is not checking whether someone knows a methodology or has run a Gantt chart before. It is working out whether you can hand them something that matters, with a real deadline and trust them to land it. Be honest about what the role is actually being asked to carry, because coordinating a tidy work stream and owning a programme that the business cannot afford to have slip are not the same job, and hiring for one when you need the other is where it usually risks going wrong.
Test for judgement, not method. The questions that reveal the most are about the moments that don’t go to plan: what they did when a project was already behind and the sponsor wanted to hear it was fine, when two senior people wanted opposite things, when the honest status was uncomfortable and the easy one was a lie by omission. We look at real situations people have steered through, because how someone behaves when a delivery is wobbling tells you far more than how fluently they can describe a framework.
And weigh temperament as heavily as track record. The people worth hiring are careful about what they promise, quick to raise a risk while there is still time to act on it, and able to tell a room full of senior stakeholders something they don’t want to hear without flinching or dressing it up. In a business where a stalled programme burns money every month, that steadiness is worth more than another certification on the CV.
Hiring for the frameworks someone has collected, and overlooking whether you would trust them when it counts, is the mistake we see most.
WHY LEVELS MATTER
Understanding seniority.
In delivery, seniority isn’t really about how big a project someone can run, it’s about how much uncertainty they can absorb before it reaches everyone else. The further up you go, the messier and less defined the project you’re handed, and the more you’re expected to turn that mess into something a team can actually get on with. That’s the real ladder. Here’s what it tends to look like.
-
A junior delivery professional is given work that's already been shaped for them, a clear plan, defined tasks, and asked to keep it on track and flag when something slips. The judgement calls are made above them, and that's exactly right at this stage. What you're looking for is someone reliable, organised, and genuinely curious about why things run the way they do.
-
A mid-level delivery professional is trusted with a whole project and left to get on with it. The plan is theirs to build and defend, the day-to-day problems are theirs to solve, and they only escalate the things that genuinely need it. They've stopped just running the process and started owning the outcome.
-
A senior delivery professional is handed the ambiguous, the political, and the already-on-fire, the work where the goal keeps moving and half the difficulty is people. They make calls with incomplete information, manage upwards as much as down, and are measured on the disasters that quietly never happened as much as the projects that landed.
-
A lead or principal delivery professional operates where there often isn't a plan yet, just an intent, competing priorities and a lot of money riding on it. Their job is to bring order to that, decide what gets done and what waits, and hold the whole thing steady when any one part could pull it off course. At this level the work is almost entirely judgement, and the cost of getting it wrong is measured in the whole endeavour, not a single project.
Skills that command a premium.
In delivery, the premium does not follow the busiest looking work. It follows the work a business most needs to trust will actually land.
People who can maintain a plan and chase actions are relatively plentiful, so the rate for pure coordination is under pressure. The money has moved to the people who carry real accountability: programme managers who can hold a complex, political delivery together, product owners who can be trusted to decide what is worth building, and the few who can walk into a troubled programme and turn it around.
A working command of both waterfall and agile still pays everywhere, because most real delivery needs both. In banking, telco and the public sector, anyone who pairs delivery skill with a genuine grasp of risk, governance and stakeholder politics commands a premium of their own, because that combination is rare and the cost of a stalled programme is high. Across all of it, the value sits with people trusted to own an outcome end to end, not those running the coordination that a tool or a template can increasingly absorb.
For businesses, that means the scarce, expensive skills are usually the ones that hold a delivery together under pressure, not the ones with the most impressive certificate list. For professionals, it means depth in the parts the market struggles to trust, delivering bad news, holding scope, landing the thing that matters, is worth more to your earning power than another framework on the CV.
Understanding the salary package.
In delivery roles, the base salary is one of the least reliable ways to compare two jobs, because so much of what a role is worth sits outside it.
Some of it is the usual: medical aid and retirement, where how much the employer contributes varies a lot, and bonuses or equity that can matter more than base pay over a few years. Delivery has its own wrinkle too, in that a lot of senior people move between permanent and contract, so the real comparison often isn’t one salary against another, it’s a stable package against a higher day rate with none of the security.
Then there’s the part that never appears on an offer letter, but shapes your next few years more than the number does. It’s whether you get handed bigger, messier, higher stakes programmes. Whether a senior leader actually backs you when it gets hard. Whether you’re trusted to own delivery, or just kept busy administering it. That last one especially separates a career that compounds from one that plateaus on a decent salary.
None of which means the number doesn’t matter, it just isn’t the part you’ll remember. Six months in, what shapes how you feel about a job is the work, the backing, and whether you were trusted to actually run things, not the figure you signed for. That’s the part worth weighing hardest.
THE COST
Contract vs Permanent.
Contract works differently in delivery than in most fields, because of what you’re actually hiring. With a technical contractor, you’re buying a skill for a stretch of work. With a project or programme contractor, you’re buying someone to hold the wheel, to carry the relationships, the running judgement calls and the quiet knowledge of where the real risk sits.
Plenty of delivery work has an obvious shape and a finish line, a system implementation, a transformation programme, a rescue job on something already off the rails, a burst of work you’d never build a permanent team around. For that, an experienced contractor is often exactly what’s needed, someone who’s landed this kind of thing before, brought in for precisely as long as it runs. The day rate looks steep next to a salary, but you’re not paying for benefits or notice, you’re paying for someone who can walk into the middle of something messy and take control of it, fast.
The part worth thinking hard about is what happens at the end. When a delivery contractor leaves, they don’t just take a skill with them, they take the context, the history, the unwritten understanding of how the programme actually works and who to call when it doesn’t.
Businesses that use contract delivery well plan for that from day one: they’re deliberate about capturing decisions, building the relationships beyond one person, and making sure the handover is real rather than a final status report. For the person deciding between the two, contract delivery pays better by the day and throws you into a run of high stakes problems to solve and move on from. What you give up is the continuity, and the deeper trust that only comes from staying to live with the results of your own calls. That trade suits some people, and some stages of a career, far more than others.
Project & Programme Management Salaries in South Africa
FOR CONTRACTOR ROLES
Seniority
Indicative hourly rate
> Junior delivery professional
R450 – R550
> Mid-level delivery professional
R650 – R800
> Senior delivery professional
R900 – R1200
> Lead or Principal delivery professional
R1350 – R1750
FOR PERMANENT ROLES
Seniority
Annual cost to company
> Junior delivery professional
R600K – R750K
> Mid-level delivery professional
R900K – R1.2M
> Senior delivery professional
R1.2M – R1.6M
> Lead or Principal delivery professional
R1.7M – R2.3M
Figures are drawn from Acuity’s own placements across the South African market and are indicative ranges, not quotes. Actual pay and rates vary with specific skills, sector, location and how in-demand a role is at the time. Contractor rates are excluding VAT. Last reviewed: July 2026
IF YOU'RE BUILDING A CAREER
Making your next move
a good one.
The best delivery careers aren’t built by moving up a title ladder, exceptional growth is built by taking on progressively harder projects to land, and being able to prove you landed them. A programme with real money and real politics on it teaches you more, and does more for where you can go next, than an impressive sounding role, babysitting work that was never going to fail. So when you weigh a move, look past the title on the offer and ask what you’ll actually be trusted to own, and how much harder it is than the last thing you pulled off.
It’s worth getting good at telling that story, too, because anyone can list the methodologies they’ve been trained in. A serious employer is listening for a delivery that went sideways and how you handled it, the call you made when the information was incomplete, the moment you had to choose between the easy answer and the right one. That’s what shows whether you can actually deliver, or only administer, and it’s the thing most people never learn to talk about well.
Which is where we come in. At Acuity, we’d rather understand where you’re trying to get to than run your CV past the nearest opening. We take the time to learn what you’re good at and what you want next, and only bring you roles that move you in that direction. Sometimes that means telling you a role isn’t right for you, even when it’s there for the taking. That’s what being a good career and growth partner actually looks like.
COMMON QUESTIONS
Project & Programme Management
questions, answered.
FOR BUSINESSES LOOKING TO LEAD, BUILD & SCALE
Our projects keep slipping even though we have plenty of PMs. What are we missing?
Usually it is not more coordination, it is accountability. Plenty of people can keep a plan updated; far fewer will make the hard call, hold scope when the business keeps adding to it, and tell a sponsor the truth while there is still time to act.
If deliveries drift despite a full team, the gap is often seniority and judgement, not headcount. We can help you work out which of your roles actually need someone trusted to own the outcome.
How do we know whether a candidate's certifications actually mean anything?
On their own, not much. A PMP, Prince2 or a stack of Agile badges tells you someone has learned the vocabulary, not that they can hold a programme together when it starts to slip. Treat certifications as a floor rather than a signal of seniority.
What matters more is whether a person can pick the right approach for the work in front of them, run a fixed-scope build one way and a shifting product another, instead of forcing every delivery through the single method they were trained in. We help you look past the certificate to the delivery record underneath it.
Should we build a permanent delivery team or bring in a contractor for the programme?
It depends on whether the work has an end. A transformation or a system rollout is a defined programme with a finish line, and a contractor sized for it makes sense.
Running delivery as an ongoing capability is permanent work. The common mistake is hiring permanent heads for a one-off push, then carrying the cost long after it is done.
How long does it take to hire a strong project or programme manager in South Africa?
Longer than most teams expect at the senior end, because the people who can genuinely be trusted with a high-stakes programme are usually working and not actively looking.
Budget for a proper search rather than a quick fill, and be ready to move once you find the right person, since strong delivery people rarely sit on the market for long.
FOR PROFESSIONALS EXPLORING
Should I specialise or stay broad?
Early on, breadth helps you find where you are strong, whether that is agile delivery, complex programmes or turning troubled projects around. After that, the market rewards depth in the areas it struggles to staff and trust. We can help you read where the scarcity sits and where your earning power actually grows
I don't have a formal PM qualification. Does that hold me back?
Less than you would think. A certificate helps you get past a filter, but delivery is judged on what you have actually landed.
Plenty of strong PMs came up through the work rather than the classroom. A visible track record of programmes delivered tends to speak louder than the badge on its own.
What would make me stand out?
Evidence that you can be trusted when things get hard. Anyone can list methodologies; far fewer can walk through a programme they rescued, a scope fight they held, or a difficult call they made and stood behind. Being able to explain your reasoning, including what you would now do differently, is what separates people.
Do you place contract and permanent roles, and can you help with remote work?
Yes to all three. We work across contract and permanent delivery roles, and remote and hybrid arrangements are a growing part of what we handle. We will talk through the trade-offs honestly, since a higher day rate or a remote setup is not automatically the right move for where you are.