Home
Need edit access? 1. Create an account 2. Send your username to Mark B
Beta assessment date: Monday 20th June, 12am - 4pm
Read about the beta phase in the Service Manual
Assessment Demo - what we will show and how.
1. User Needs - Understand user needs. Research to develop a deep knowledge of who the service users are and what that means for the design of the service.
2. Ongoing Research - Put a plan in place for ongoing user research and usability testing to continuously seek feedback from users to improve the service.
3. The Team - Put in place a sustainable multidisciplinary team that can design, build and operate the service, led by a suitably skilled and senior service manager with decision-making responsibility.
4. Agile - Build the service using the agile, iterative and user-centred methods set out in the manual.
5. Frequent iteration - Build a service that can be iterated and improved on a frequent basis and make sure that you have the capacity, resources and technical flexibility to do so.
6. Technical architecture - Evaluate what tools and systems will be used to build, host, operate and measure the service, and how to procure them.
7. Data security - Evaluate what user data and information the digital service will be providing or storing, and address the security level, legal responsibilities, privacy issues and risks associated with the service (consulting with experts where appropriate).
8. Code sharing - Make all new source code open and reusable, and publish it under appropriate licences (or provide a convincing explanation as to why this cannot be done for specific subsets of the source code).
9. Open standards - Use open standards and common government platforms where available.
10. Test environment - Be able to test the end-to-end service in an environment identical to that of the live version, including on all common browsers and devices, and using dummy accounts and a representative sample of users.
11. Offline plan - Make a plan for the event of the digital service being taken temporarily offline.
12. Intuitive design - Create a service that is simple and intuitive enough that users succeed first time.
13. GOV.UK UX - Build a service consistent with the user experience of the rest of GOV.UK including using the design patterns and style guide.
14. Digital takeup - Encourage all users to use the digital service (with assisted digital support if required), alongside an appropriate plan to phase out non-digital channels/services.
15. Data analysis - Use tools for analysis that collect performance data. Use this data to analyse the success of the service and to translate this into features and tasks for the next phase of development.
16. KPIs - Identify performance indicators for the service, including the 4 mandatory key performance indicators (KPIs) defined in the manual. Establish a benchmark for each metric and make a plan to enable improvements.
17. Performance platform - Report performance data on the Performance Platform.
18. Minister test - Test the service from beginning to end with the minister responsible for it.