...to an in-house user researcher. GDS were not assured how the current team would be able to design/test/code quickly without this support being in place, particularly for a Live service....
...user research and analytics. Make source code open and reusable - point 15 For beta assessment the panel expect to see steps taken for this project to be coded in...
...face-to-face support. The service team knew the cost of phone support, and are budgeting a comfortable contingency for provision of face by face support, the final cost of which will...
...code rather than flat HTML wireframes. Specifically, before the service returns for a Beta assessment, it’s essential that: stronger user stories are developed a ‘real’ fully coded service is used...
...security, and user research covered attitudes to disclosure or anonymity of potential job-sharers’ personal details. The source code needs to be published in a public repository before the service proceeds...
...Use of open standards and open source code; the team have made use of open source code and contributed their own. Collaborative working across the team and different locations (using...
...can refer to a range of circumstances from a simple code issue, like the misplacement of a bracket, to a fundamental misunderstanding of the problem you are trying to tackle....
...any issues lie. The technical architect also described what measures are in place (sanitisation, workflows, role access) to ensure that data is handled appropriately. Call centre code has been looked...
...code-quality metrics (e.g. CodeClimate). Open source Project needs a clearer plan of what code will be released and when. Design Will need to review pinch points of failure as prototype...
...website can be iterated quickly; code changes to the current site are made only once once or twice a year. They have a well-thought-out set of environments that allow continuous...
Sign up to get updates direct to your inbox and stay informed about improvements to digital products and services in government.