Scrum Masters Are Being Hired Again. That Is Worth Noticing.
After what has felt like a rather extended period of nothing very much, agile roles are appearing in UK job listings again. Scrum Master vacancies are up. Release Train Engineer postings, which had become something of a rarity through the belt-tightening of 2024 and 2025, are visible once more. The median UK Scrum Master salary has ticked up to £73,750, a 3.7% rise year on year, which is the kind of number that tends to move when employers are competing for the same small pool of people rather than quietly hoping they will not need to hire at all.
It would be unwise to read too much into a few months of data. The agile job market has been erratic enough recently that any trend deserves some caution before it gets a victory lap. That said, the direction of travel has shifted, and the specific roles appearing matter as much as the volume.
What the Listings Are Actually Telling Us
Release Train Engineers do not tend to appear in job listings by accident. They are senior, expensive, and very specifically useful: you hire one when you are running a SAFe Agile Release Train and need someone qualified to keep it moving. Their reappearance in reasonable numbers suggests that enterprise programmes, which were deferred, restructured or quietly left on the shelf through the more difficult months of the past two years, are now being restarted. Someone, somewhere in a number of large organisations, has signed something off.
There is a related pattern worth noting. Recruiters who track the UK tech market have observed that Business Analyst roles tend to return before developer headcount is increased, which is one of the more reliable early signals that an organisation is moving from planning into execution. Strategy solidifies, budgets get committed, and the people needed to define the work appear in advance of the people needed to do it. That pattern has been visible in UK tech hiring since the beginning of this year. Agile delivery roles appearing alongside it is consistent with the idea that some of the transformation programmes waiting in the wings are now getting their moment.
The new financial year is probably doing some of the work here. April tends to unlock what December promised but did not quite deliver. In our experience, Q1 of the new UK financial year is when training and capability-building decisions that have been discussed for months finally get a purchase order attached to them, which is a less romantic way of saying that things actually happen.
Hiring Your Way to Agility
The instinct, when an organisation decides it needs more agile capability, is often to hire. There is nothing wrong with this as far as it goes: bringing in experienced practitioners can accelerate a programme, and there are genuine cases where a senior hire is the right answer. An RTE with ten years of SAFe delivery experience will add value from day one in ways that a newly certified internal candidate may not.
The complication is that hiring is only ever half the answer, and sometimes less. A Scrum Master brought in from outside carries their own mental model of how things should work, which may or may not match the organisation they have joined. They also tend to leave. The teams they work with, meanwhile, may acquire a functional agile process without ever quite understanding why any of it is structured the way it is, which makes them rather dependent on that individual continuing to show up. We have seen this play out often enough that it has a slightly familiar quality: the transformation that works well for two years and then quietly unravels when the person holding it together moves on.
The organisations that handle this best tend to do both things in parallel: targeted external hiring at the senior level, combined with a deliberate effort to build genuine agile capability across the wider team. The training investment is not the glamorous part of the plan, but it is the part that determines whether the programme still exists in three years.
A Note for L&D Teams
If your organisation is in the early stages of planning a transformation, or restarting one that was interrupted, the training question tends to get left until later in the process than it should. The common sequence is: announce the programme, hire a few senior practitioners, design the operating model, and then ask L&D to arrange some training for the teams. By that point the timeline is already under pressure and the training gets compressed or deferred.
Getting ahead of it, even by a few weeks, makes a meaningful difference. Understanding which roles need which certifications, at what level, and on what schedule is not a complicated exercise, but it does require someone to have done it before the programme launch rather than after. If that conversation would be useful, we are here.
The winter has been a long one. Late spring feels, tentatively, like the right description for where the market is now. It would be a shame to spend it unprepared.