Guides to agile delivery in government
Reference pages for people who deliver digital services in government. Each one answers a question we are asked on our courses, and links to the official guidance it draws on.
-
The 14 points of the Service Standard and what to show a panel
GDS sets 14 points that a government service team has to meet. Here is each one in GDS's own words, with what a team shows the assessment panel.
-
Discovery, alpha, beta and live: what each phase is for
Government services go through discovery, alpha, beta and live. This guide sets out what the team does in each phase and what it has to show before the next one.
-
How to prepare for a service assessment
At a service assessment a panel spends about four hours checking a service against the Service Standard. This guide covers booking, who to bring, what the panel asks and what each result leads to.
-
Flow metrics and forecasting for government teams
Four measures from your own board show how work moves through your team, and with them you can give a delivery date with odds.
-
The delivery manager role in government, explained
A delivery manager in government is accountable for the delivery of products and services. This guide covers the four levels, the nine skills and how the role differs from a Scrum Master and a project manager.
-
How to buy agile training through RM6219
RM6219 is the Learning and Training Services DPS, now run by Government Commercial Agency. This guide sets out the two ways a buyer awards a contract from it and how to find us on it.
-
Agile glossary for civil servants
Thirty-two terms you will hear on a government delivery team, each defined in a sentence or two. Where GDS or the profession has its own wording, we use it, and half the entries link to the government page they come from.