As Stephen Foreshew Cain said Sprint 16 was a great day and Government as a Platform was very much at the heart of it. In case you missed it or weren’t there, here’s a quick recap on the Government as a Platform highlights from Sprint 16.
We’ve drafted some principles (similar to the GDS design principles), to define how things in the Government as a Platform toolbox should be built and run.
The Civil Service Digital Team are building better tools for civil servants to do things like performance reviews, expense claims, booking courses and gathering data. But they cant do this in isolation. They want to work alongside users (ie civil servants) on an ongoing basis to hear about their needs and get their comments and feedback.
Seb Tallents writes about Government as a Platform as a range of products, which will form a single platform on which service teams can build brilliant transactional services.
We’re seeing an increasing number of government services offering, or looking to offer, web (or live) chat as an alternative contact channel for their users.
This week we took some time to map out the stages that it takes to be granted a shotgun licence.
Rosalie Marshall explains the user research that's helping to shape guidelines for developer documentation, including documentation for APIs.
Harry Trimble blogs about the collaboration that went into, and the complexity behind, the map of driving services. He talks about relationship between users, transactions and services.
The government notifications platform will be called GOV.UK Notify. This post explains what the platform will offer service teams in departments and agencies, and how developers will be able to get easy access to the platform to integrate GOV.UK Notify into their services.
Technical architect, Anna Shipman, explains the reasons for choosing Cloud Foundry as the technology for Platform as a Service.