GOV.UK Verify: Technical delivery update, 9 February 2016
...reducing our technical debt. Here’s what we’ve been working on since the last update, and what we plan to do next. Increasing adoption of GOV.UK Verify We want departments across...
...reducing our technical debt. Here’s what we’ve been working on since the last update, and what we plan to do next. Increasing adoption of GOV.UK Verify We want departments across...
...completed, work to be done that day and any blockers preventing us from completing that work. After standup we look at the stories on the wall and split ourselves into...
...second step can be a code sent to a mobile phone (one of the more commonly used methods), or it can be another method such as a code communicated to...
...and keyboard while the rest of the mob act as ‘navigators’ by suggesting what source code needs to be produced. Not everybody will be part of the mob at all...
...the behaviour that we’ve been seeing repeatedly in our fortnightly testing. For example that: driving licence, passport and current account are the most popular forms of identity evidence people gravitate...
...that each certified company is a data controller under the terms of the Data Protection Act (1998), with their own internal privacy management processes, we determined that they should complete...
...skipping through sections that the screen reading software identifies using the header tags in the code. However, we realised that some of the pages in GOV.UK Verify don’t use headers...
...about our work ahead of the assessment We could only have a limited number of people at the assessment but wanted to demonstrate that team members from across the programme...
...and improve the service continues at pace. Here’s a summary of what we’ve been working on since our last update back in July and what we plan to do next....
...do know is that there are some valuable lessons that we’ve learnt from this change, which we can apply to further iterate and improve GOV.UK Verify. What we learnt We...