Agile delivery encourages teams to build quickly, test what they’ve built regularly and improve (iterate) their work based on regular feedback from users and performance data.
The principles behind agile delivery are set out in the Agile Manifesto (2001).
Agile delivery is split into 4 different phases: Discovery, Alpha, Beta and Live. There is more information about each of these stages below.
Digital First Service Standard assessments take place during the Discovery, Alpha and Beta phases of a project.
Further information on Agile can be found on the gov.uk website.
The Scottish Government’s Digital Transformation Team offer agile coaching for organisations.
Future public services in Scotland need to be flexible. When services are delivered using agile methods, it allows them to be changed quickly and improved regularly.
Service teams across Scotland must use the agile approach to delivering a service as part of the Digital First Service Standard.
If you think you can’t use agile to deliver your service, please raise this in your first conversation with the Digital First team, contact them at OCIOAssurance@gov.scot.
In Discovery you will be researching so that you understand if a service should be delivered. If your research suggests it should, discovery should help you prioritise what you need to do for alpha.
Discovery is completed over a short period of time – ideally 3-4 weeks.
When you finish Discovery, you should:
Further information on Discovery is available on the GOV.UK website.
In Alpha you will be testing the assumptions you’ve made from the research in your Discovery. To do this you will be testing prototypes with users and stakeholders.
Alongside testing the prototypes, you will be deciding how to build the service. You will need to prove it is technically possible to deliver the service at the end of Alpha.
Most Alphas are 8 weeks long and include 3 stages:
When you exit Alpha, you should:
Further information on Alpha is available on the GOV.UK website.
In Beta you will be developing a working version of your service. This is sometimes called a minimum viable product (MVP).
It must be able to handle real transactions (for example if your service includes a search function users must be able to search and get results).
Beta involves releasing a version of your service to the public.
The length of time your service will spend in Beta depends on the scale of your project. Until your service is live, you will need to have a Beta banner. There is a Beta design pattern you must follow.
When you exit Beta, you should:
Further information on Beta is available on the GOV.UK website.
When your service is Live the focus is on continually improving it. You will improve your service with:
Your service can’t become Live until it has been through the Discovery, Alpha and Beta.