...because the prototypes are no longer being built using HTML, with Axure being used instead. We would expect fortnightly sprints to become the norm once “real” code is used again,...
...team were keen to make code open source, and understood the benefits and challenges involved in working in the open. Service availability The team shows a clear understanding of the...
...able to ensure that internal and external stakeholders are being kept up to date with progress. The technology choices are embracing open source and all code is being made available...
...conform to the service design manual and design patterns. The team will need to include a front-end developer that can quickly iterate the code and make changes to the template....
...in Newcastle and London e.g. Researcher, Design etc. There is a good relationship with web ops in London and team members have spent time with web ops learning to code...
...None however are open source. There is a program reluctance to share code for security/fraud prevention reasons. Whilst the team appreciates these concerns, the panel would ecourage a much stronger...
...developers, the team cannot have confidence that the code delivered to web browsers works for service users on the devices and browsers they use, or in a way that is...
...with them to ensure that their non-repudiation requirements will be met. Coding in the Open The team are committed to open sourcing the code for the service from the outset....
...publishing platform, which concerned the panel before confirming that the team are capable of making their own amendments to the codebase should GOV.UK’s roadmap change. Security is being considered well...
...is not available and confirm what the approach for this will be in public beta; ensure that they are evaluating code for sharing; implement Analytics and discuss (as already scheduled)...