There will be three environments: dev, staging and live. Deployment will be controlled by two main Git source control…Read more on 5. Build a service that can be iterated and improved on a frequent basis
The Beta delivery team currently consists of; Product/Service Manager Associate Product Manager Delivery Manager Business Analyst User Researcher/Information Architect…Read more on 3. Put in place a sustainable multidisciplinary team that can design, build and operate the service
All technology used on the Beta is open source and well supported. A ‘boring is better’ approach has been…Read more on 6. Evaluate what tools and systems will be used to build, host, operate and measure the service, and how to procure them.
The ONS website sits outside of the GOV.UK ‘brand’ and as such has design patterns and user experience requirements separate…Read more on 13. Build a service consistent with the user experience of the rest of GOV.UK including using the design patterns and style guide.
All of our code is either based on existing open source libraries or is released itself under an open…Read more on 8. Make all new source code open and reusable, and publish it under appropriate licences
The team works according to agile methods without being slavish to a particular methodology. We tend to talk about small…Read more on 4. Build the service using the agile, iterative and user-centred methods set out in the manual
In the spirit of the tenth GDS design principle I am planning to share a series of blogposts over…Read more on Open approach to Service Assessment