...of the public beta release the team must: make their source code open and reusable. The team explained that the code was written to be shared and reusable but it...
...code being completed and deployed was measurable in days however, currently achieved 4 big releases per year. The panel would suggest that wherever it is achievable for completed code to...
...always needed our developers to write the code. The Admin App, codenamed the Onboarding App, changes this. On average a new dashboard took us weeks to develop. The app means...
...have acted on the recommendations of the previous report and have focused on user research. The service has passed the beta assessment and the recommendations listed above are within the...
...open source reusable code you should: ensure that code is opened as first priority when a new developer starts; if the repo is not public from the start there is...
...for this project to be coded in the open, with all code published on github.com in open repositories. Where this is not possible there should be a convincing explanation as...
...leased line into both data centres or reduced dependency on leased lines. Open Source Only a small proportion of code has been open-sourced. One reason for this was the presence...
...reflect the high data protection requirement. The source code was peer reviewed by GDS before being finalised by the supplier. At present security requirements are too entangled with the general...
...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...
...plans are in place to continue on this basis. The paper checklist that has been created to help users gather the information they need beforehand is also well thought through....