Run through 'tech & ops health check'

[36degrees]

What

Run through the 'tech & ops health check' checklist - 'a handy list of good practices for a team to self evaluate against'.

The health check covers the technical and operational aspects of a service only. It does not cover user-centered design or agile ways of working.

Why

The tech & ops health check should help us to identify possible gaps or areas to improve. This is particularly useful as we start to think about going for a live assessment.

Who needs to know

Developers, technical writers, product manager

Done when…

• [x] Run through health check with @louzoid-gds to work out which items on the checklist are relevant for the team
• [x] Go through the health check as a team of developers, scoring ourselves using the criteria provided and identifying which areas we're most concerned about
• [ ] Identify and write up cards for any follow-up actions we want to take in the next few quarters

[36degrees]

Spreadsheet is here: https://docs.google.com/spreadsheets/d/1I4aUcg5ff6rpf2C5Z1b_D0BOTHU6fgMbXn3jCzBXuSE/edit#gid=0

Session booked in with the team on Monday 9 November to go through the health check together.

[36degrees]

Off the back of the workshop, we plan to look at improving our threat-modelling processes next quarter.

Once we've done that, we should revisit the spreadsheet as lots of the areas we identified for improvement relate to our mitigation and response to threats.

Other areas that we want to look at include:

• Improve our processes for managing technical debt (#1429)
• Get visibility over performance metrics (alphagov/govuk-frontend#2076)
• Add visual regression testing (alphagov/govuk-frontend#2070)
• Improve our use of automated accessibility tools (alphagov/govuk-frontend#1971)

I think this is otherwise done now, so closing it.