In 2013, we introduced the Technology Code of Practice. This gives guidance on the best way to design, buy and build technology and digital services to meet user needs.
We've used the Technology Code of Practice to examine and challenge government spending on technology through the spend controls process. It’s given us a way to engage with departments and agencies and help them revise and improve their technology plans.
Government technology has changed a lot and huge progress has been made since the Technology Code of Practice was originally published. Our new draft takes this progress into account, while continuing our focus on the user needs that have been at the heart of the transformation of government technology.
In drafting the new Technology Code of Practice, we’ve tried to write a document which provides:
- a clear statement of what a good approach to technology looks like
- a flexible, context-sensitive framework to assess technology plans against
We want government to continue to be a smarter user of technology, and to do that government needs to be a smarter customer. The new document reflects an increased focus on good commercial behaviours.
We also want to recognise the variety of strategic, commercial and business contexts in which government technology work happens, and enable departments and agencies to deliver great technology that meets their needs.
We want the new Technology Code of Practice to:
- encourage a more mature approach to sourcing IT in government, supporting departments moving away from large aggregated contracts to the preferred multi-supplier contracting model
- continue to promote competition and diversity of technology suppliers to government, both by improving buying practices and by making government a more attractive and willing customer of innovative, new technologies
- help people determine the ideal target state for their technology services and make better decisions on when to design and build solutions and when to use off-the-shelf products or commodities
- promote a more adaptive approach to technology, based on clear principles of good practice as well as the context in which technology will be planned, bought and used
Updating the controls process
Alongside reviewing the Technology Code of Practice, we’re also looking at the spend controls process and how we assess departmental technology plans. We’ll be publishing more details on that in the future.
We need your help
This is an important document. So, we’re publishing this draft version, to give you the opportunity to help us make it better.
We need your input on:
- whether you understand what this document is for
- whether you understand what we think a good approach to technology is
- whether you agree with our view of what a good approach to technology looks like
- whether you think you could use this document to inform your technology plans
- whether you understand what the GDS spend controls will be looking for
Tell us what you think. Tell us what you think is good and what you think is bad, where we’ve got it right and where we’ve got it wrong. Email us or comment below, and we’ll make sure to take those views into account as we iterate the Technology Code of Practice.
Please note the deadline for feedback is Friday 8 July 2016