The agile community exists to:
- share information about how to use agile ways of working in government
- give agile practitioners the opportunity to share experiences, observed behaviours and best practice
- give people a space to discuss and challenge the way agile methods are used to deliver government projects and products
Who the community is for
You might be interested in the community if you use (or want to use) agile methods to deliver government projects or products.
You don’t have to be in a software development role to join.
Join the government agile delivery Google group, the main cross-government forum for discussing agile (request access using your government email address).
You could also join the cross-government #deliverymgmt Slack channel.
Use these resources to learn more about agile in government:
- GDS blog - includes stories, lessons and case studies about agile from across government
- MOJ Digital blog - posts from the Ministry of Justice about their experience of using agile
- Home Office Digital blog - posts from Home Office staff about what they’ve learnt about using agile
Agile in the Service Manual
These guides show what we currently believe to be best practice for delivering government services in an agile way:
- Agile and government services: an introduction
- Agile methods: an introduction
- Core principles of agile
- Creating an agile working environment
- Agile tools and techniques
- Set up a team wall
- Writing user stories
- Planning in agile
- Governance principles for agile service delivery
- Measuring and reporting progress
- How the discovery phase works
- How the alpha phase works
- How the beta phase works
- How the live phase works
- Retiring your service
Help us keep the Service Manual up to date by:
- contributing to community discussions
- telling us if something is wrong or out of date using the feedback link at the top of each guide
Added guides to how the discovery, alpha, beta and live phases work, and 'Retiring your service'.
Guidance first published