mcoulthurst
commented
5 years ago There are two prototypes. One for service users to find EPC's, assessors or to opt out of the register. The second is for service providers and data consumers and requires authorised access to different aspects of the data.
The first version of the prototypes were built using the discovery wireframe for p1 and the existing service as a base line for p2. This was subject to expert review and user feedback.
Feedback was captured as issues in Github and tagged with appropriate labels.
Groups of issues were picked up as part of the weekly sprint and changes and additions made to the prototypes on a daily basis. In some cases reviews of iterations were removed based on feedback, eg different patterns used to capture lodgement data.
The two prototypes have been continously updated and deploy to Heroku during the course of the Alpha phase. The Service users prototype (p01) was updated 59 times. The Service providers and data consumers prototype (p02) was updated 57 times.
https://mhclg-epc-alpha-prototype-01.herokuapp.com/ https://mhclg-epc-alpha-prototype-02.herokuapp.com/
To pass the alpha, beta and live assessments, you usually need to:
explain what you’ve built in that phase and why you built it
describe the lifecycle of a user story from user research to production
show you understand how your service is built to meet user needs
explain your process for identifying and prioritising insights from user research
show you can move user stories quickly and smoothly between user research and production show there’s minimal risk associated with the technology you chose
prove you have the ability to deploy software frequently with minimal disruption to users
show you’re analysing user research and using it to improve your service
show you’re solving any technical problems you’ve found