...to why. Improving the service To be able to update and improve the service on a very frequent basis, the service team must continue to shorten the build pipeline with...
...and constantly improving the service. A strong commitment to open sourcing the code (with all code being placed on Github), as well as to open data with each page being...
...will enable the team to understand those users’ needs for support and start to make decisions during the beta phase about how, specifically, to meet those needs. The service has...
...etc. Open Source Code The panel were encouraged to hear HMRC are making progress in this area, but we are still yet to see any service code published. Publishing source...
...team to cultivate support for the project in a context of highly complex stakeholder relationships and prevailing resistance to change. However in order to meet the required standard the team...
...The first step was to import all ten years of rough sleeping data into our SQL database. Once all the data had been located it was imported into the database...
...financially? We’ve had 5,881 visits to the service design manual search over 6 months, and reckon it took about £3,000 worth of internal developer time to build. The code should...
...attempting it. We want to get other analysts talking about our numbers and the choices we take with data - and hopefully, helping us to make more insights and better...
...blog. If you want to learn more about the service or if you’re interested in using tariff data to power your services then get in touch with the team directly....
...forward to announcing the successful candidate soon. Look out for a further blog post from the new community manager when they start to understand their priorities and how to get...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.