'No mission longer than 11 weeks' - GOV.UK adopts new way of working
Projects can vary in scope, but must always wrap up inside a quarter
The GOV.UK roadmap of initiatives is reviewed and updated at least every three months Credit: GDS
The team behind the GOV.UK web infrastructure has implemented a new way of working, after deciding that its previous models created projects that were “protracted and [where] delivery was hard to show”.
GOV.UK has a publicly available roadmap of “missions”. Although this roster is updated every quarter, the organisation concluded that its projects felt like they were taking too long and the results were difficult to demonstrate.
- GDS to audit all GOV.UK pages by 2020
- GOV.UK Notify begins local government rollout
- GDS seeks more Verify developers in latest bid to get service working at scale
Product managers at GOV.UK must now undertake projects of no longer than 11 weeks. The aims of that project may be expanded or reduced but, whatever happens, it has to conclude within the space of one quarter.
“The scope of the mission is flexible but the length of the mission is fixed,” GOV.UK said. “It might be the case that a theme extends over the course of the year, but we want iterative and complete delivery every 11 weeks, in case we need to change direction or stop.”
The organisation claimed that this length of time is optimal for delivering the most value.
“We feel this structure allows us to build and develop products to a stable state, in a responsible way,” it added.
Share this page
CONTRIBUTIONS FROM READERS
Please login to post a comment or register for a free account.
Departments look to sign joint deal with a software provider and a system integrator
Public Accounts Committee warns that lack of support could imperil delivery
Minister says that all public-sector customers have now moved to alternative provider
In a piece written for PublicTechnology, parliamentary secretary Alex Burghart discusses progress with One Login and the significance of legislative changes
Related Sponsored Articles
The traditional reactive approach to cybersecurity, which involves responding to attacks after they have occurred, is no longer sufficient. Murielle Gonzalez reports on a webinar looking at...