Fellowship Digital Services: Beta Phase Sprint Notes 6

In this Sprint, we held a technical workshop to discuss the MyRSA updates and SSO implementation within the context of the Beta roadmap. We also outlined our plans for progressing Beta testing.

A reminder of the project's focus: this beta project is focused on enhancing existing and implementing a new technology at the RSA called Circle, to help improve how Fellows engage and contribute to the RSA work and collaborate with other Fellows.

For further detail see Beta Phase Sprint Notes 5

What happened in Sprint 6

The goal we set out for Sprint 6 was to design the end-to-end user journey, and plan
how the service needs to develop technically to enable this journey. This goal was
too big to complete in a single sprint, but it was a priority to get started on.
During this sprint, we also:

• We held a technical workshop with the RSA’s technology partners, focused on MyRSA and the single sign on (SSO) requirements
• led a content and engagement workshop with RSA stakeholders
• presented project updates to the Steering Group
• dxw refined the beta testing plan
• spent time discussing how to improve our ways of working together, to ensure the successful delivery of the project and beta service.

Designing the end-to-end journey

At the start of the sprint we identified which parts of the end-to-end user journey to focus on first, and began designing the interaction and content for these parts of the service. We reviewed the designs at the end of the sprint, providing feedback and suggesting change.

Technical workshop

The technical workshop was delivered in two parts focused on i) MyRSA and ii) SSO. In the MyRSA session we explored what we need to do from a data and technology point of view to realise the improvements required by MyRSA outlined by the beta roadmap.

The SSO part centred around playing back as well as further discussing what we have learnt so far about the possibility of introducing the SSO option. The SSO could potentially integrate Circle and other technology solutions used by the RSA to allow
the user to log in only once, rather than having to log individually to each platform. Both parts of the workshop went very well and had a great engagement from the participants which included various stakeholders from the RSA and their technology.In the next Sprint 7, we will deliver another technical workshop focused on communications and preferences.

Beta testing plan

Following the design of the service’s end-to-end journey, we progressed our plans for testing the service with users. This is to ensure the new service provides Fellows and other service users a positive experience, meets the service vision and beta goal, and is accessible, reliable and secure. We drafted a beta testing plan, which outlines different groups of users that we suggest take part in the testing to ensure diversity and consider the needs of as many

different user groups as possible. We have detailed the format, timeline and structure of how we could deliver three types of testing with the Fellows - unmoderated, activity led, and functional testing.

Next steps

We have 4 sprints left before we start rolling the service out. The core focus for the upcoming sprints is to build the MVP version of the beta service and test it with users to ensure their needs are reflected.

The Sprint 7 goal is to design the end-to-end user journey, start to form a technical plan to build the service and enable the journey, and gain clarity about how preferences should be handled.