This is a guest post from our [much more than a] Business Analyst Alison Sarioglu –> It is well know…Read more on Time after time [the 09.30 problem]
The eagle eyed amongst you will have noticed we pushed a LOT of changes to the Beta this evening. It…Read more on Beta Release Note: 071015
At the end of August Jonathan, our User Researcher, headed down to London for two days of one-on-one interviews with…Read more on Getting critical
Our Beta project is in full swing now and we are receiving a steady stream of feedback – all of…Read more on Roadmap revealed
On Monday we quietly removed the password from the ONS Beta website and made it public for the first time….Read more on Beta begins
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