Agile for senior civil servants: what you need to know
You can sponsor agile delivery well without becoming a practitioner. Here are the five things to know, what to leave to the team and what to do in your first month.
To sponsor agile delivery well as a senior civil servant, you have to know five things: why the team’s plan changes, which decisions are yours, how to see progress first hand, how to read a forecast and which approvals still apply. You do not have to learn the team’s methods, tools or vocabulary. Both lists are below, with links to the GOV.UK guidance behind them.
What agile delivery is
The Government Digital Service (GDS) tells departments in the Service Manual that they must use the agile approach to build and run government digital services. An agile team researches, designs, builds and tests at the same time, in small steps, and changes course when users show them something is wrong. They start small in the discovery and alpha phases, build the real service in beta and go live once they have evidence that it works for the people who use it.
GDS gives the reason on the same page. A team that fixes every requirement at the start can spend 18 months building a service that no longer fits the policy, the technology or what users need. GDS says building in sequence is necessary for things like bridges and buildings, but works less well for a service when technology changes quickly. With a new service, nobody knows what will work until users try it.
Five things you do need to know
Expect the plan to change
A team doing new work learns something each week that they could not have known at the start. When they change the plan because of it, they are doing their job. Hold them to the outcome you agreed and expect the route to move.
Know which decisions are yours
In its governance principles for agile service delivery, GDS says a team should know that they have authority over the service, where that authority stops and who will help with decisions beyond it. For the biggest decisions, that person is you. GDS calls the person who runs the service the service owner. Agree with them what the team can decide alone, then answer quickly when the team brings you anything else. If the team has to wait for next month’s board to get a decision, you are paying them while they wait.
Go and see the work
GDS also says senior responsible owners (SROs) should visit teams regularly and join their meetings, particularly the show and tell, where the team demonstrates what they have built since the last one. You will learn more from half an hour watching the working service than from a written status report. If the team is not holding show and tells, GDS’s advice is to find out why.
Ask for a forecast with odds
A team can count the pieces of work they finish each week and use that record to forecast when the rest will be done. An honest forecast comes with odds, for example “an 85% chance by 6th October”. Ask which weeks of their record the team used, and ask to see the forecast again each fortnight. Our guide to reading a delivery forecast shows how.
Plan for assurance and approvals
Your programme will still be scrutinised. The National Infrastructure and Service Transformation Authority (NISTA) updated its guide to assuring agile delivery in August 2026. In it NISTA warns that no approach is a cure-all, agile included, and lists a lack of senior ownership among the common causes of failure.
The rules on spending approval changed on 1st April 2026, when the government replaced the digital and technology spend controls. Our guide to agile business cases and spend controls explains what replaced them.
What you can leave to the team
You do not have to learn Scrum, Kanban or any other method by name, and you do not need a certificate. Writing up requirements and running planning sessions are jobs for the team. The delivery manager and product manager know how to do that. A sponsor who starts directing their methods takes authority away from the people GDS says should have it.
What you do need is enough understanding to tell a team that is learning from a team that is drifting. Our ten questions to ask your delivery team are written for that.
If you would like to work through this with other senior leaders, Agile Leadership is a one-day programme for up to eight SCS and G6 leaders. Agile Awareness is a half day for leaders outside digital roles who work alongside agile teams.
What to do in your first month
Find the date of the team’s next show and tell and go to it. Agree with the service owner what the team can decide without you, and write it down. Then ask the delivery manager for a forecast with odds in place of the milestone chart, and ask for it again a fortnight later.
Questions people ask
Do senior civil servants need agile training?
You need enough to sponsor the work: why the plan changes, which decisions are yours and how to read a forecast. You do not need practitioner training or a certificate. Our programmes for senior leaders take a half day or one day.
Is agile mandatory in UK government?
For digital services, yes. GDS states in the Service Manual that departments must use the agile approach to build and run government digital services. NISTA, which assures major programmes, adds that agile can also help on other work where the requirements are unclear or likely to change.
What is the difference between agile and waterfall?
A waterfall team gathers requirements, designs, builds and tests in sequence, and users see the result at the end. An agile team does those things together in small steps and tests with users throughout, so they hear what is wrong while there is still time to change it.
What is a show and tell?
It is a regular meeting where the delivery team demonstrates what they have built or learned since the last one. GDS advises SROs to take part so that they are fully informed and can make decisions quickly.