GDS updates code of practice for government digital projects

Written by Rebecca Hill on 16 June 2016 in News
News

The Government Digital Service plans to update its Technology Code of Practice to encourage a more adaptive and innovative approach to technology use in government.

The GDS has said creating the new Technology Code of Practice is an iterative process - Photo credit: Flickr, Sebastian Wiertz

The GDS said the code, which was introduced in 2013 to provide guidance on the best way to design, buy and build technology and digital services, needs to be updated.

It published a draft version of an updated code for consultation on 15 June.


Related content

Tower of wrong
The toll of transformation - How to reduce the cost of digital project costs


The code allows the GDS to challenge government spending on technology, with the aim being to reduce the number of long-term, high-value contracts awarded.

It sets out what digital projects must demonstrate in order to be approved by the GDS, which include demonstrating value for money and that they meet other government standards, such as digital by default and open standard.

The updated code continues the drive to smaller, multi-supplier contracts, which the GDS describes as a “more mature approach” to sourcing IT in government.

The GDS says that further aims of the updated code is to push government to be more open to innovative, new technologies, saying that it wants to make government a “more attractive and willing customer” for such technologies.

In addition, the GDS says the new code will promote a more adaptive approach to technology and help people determine the ideal target for their technology services.

Unlike the existing version of the code, which outlines 21 elements that must be met by technology projects, the new code divides the principles into eight sections in an effort to offer users an easier to understand document.

The eight sections include measures that should be used to ensure and demonstrate projects are open, secure and accessible.

Other sections cover the need to use the cloud first, share and reuse data, information or capabilities, and common government platforms such as the GOV.UK components.

The final principles are that projects meet the digital service standard and comply with the greening government ICT strategy.

The code then details three principles for the sourcing of contracts.

These are to use common government solutions, such as the Digital Marketplace, to enter into “sensible” contracts – the code includes a list of what contracts should and shouldn’t commit departments to – and to fully define the sourcing strategy for the contract.

The deadline for responses to the new code is 8 July. The GDS said it would be reviewing the spend controls process separately, with more details to come soon.

Share this page

Tags

Categories

Add new comment

Related Articles

2017 in review - part one
28 December 2017

The first of a two-part recap of 2017 looks at the biggest stories and most significant developments in the first six months of the year

Crown Hosting CEO: ‘We have taken away all the cloud excuses’
14 February 2018

PublicTechnology talks to Steve Hall about the framework’s achievements so far, its ambitions for its last year, and the secret to a successful public-private joint venture  ...

Ordnance Survey looks to future as a ‘data-as-a-service’ provider
8 February 2018

Mapping agency seeks input for three-month project to define long-term data strategy, including necessary skills and technology infrastructure 

Related Sponsored Articles

Who keeps your organisation secure?
19 February 2018

BT's Amy Lemberger argues that having the right security in place to protect your organisation is no longer just an option. It is a necessity.

WATCH: Digital transformation - the key to success or a security risk too far?
13 February 2018

BT brought together some their top security experts and CIOs from well known UK organisations to discuss digital transformation and the impact that it’s having on organisations