Developmental Roadmap Q1-Q2 2022 Summary
- Lisa Clancy
Below is our planned roadmap for the next two quarters, along with a brief outline of the intended work.
These are estimated and are not guaranteed delivery dates.
Projects/Epics | Summary |
|---|---|
This will be to expand on the QA screen, utilising a similar design that we used for the new Appeals work. With tabs to add more information, with the ability to create tasks for the EPA’s, allow developmental feedback, have a full audit trail, a comments section for messaging and the ability to use file uploads. 
| |
Extensions to the user rights for Providers /Employers So we are looking at changes to allow the Provider Primary User to be able to assign other roles to other provider users, or employers and to restrict them to read only access. Also to look at allowing apprentices to be assigned to a specific Provider/Employer user. Make a change to reporting:
We will also link this to the notifications so that if you are assigned to a particular Standard(s)/Apprentices/etc then your comms are limited to those. | |
The primary change for this work is to have the “estimate completed date” calculated by the system rather than set by the users. This will mean that the only real time it can be set, is when BiL/Suspended type changes occur and then we will allow an AO to override it. So for example;
Create a new report to show apprentices that have assessments that are scheduled during the date range you specify | |
Work to allow the addition of admin and also travel time to assessment elements, to aid the EPA’s planning. We will look to add custom calendar events and sync them with external calendars. | |
Break down the submission of the QA into a 2 step process | |
Creation of a mandatory Ofqual Reasonable Adjustments drop down list, where applicable. We will also look to create a screen where you can create and manage your own lists, as a second drop down if required. | |
Currently QA Sampling is based on the components, we will look to add a system wide option to QA by Apprentice. So when a result is added, it is not automatically QAd, instead it will be held until all components have had a result added, then submitted for QA. | |
We will update the shared Standard and QA Standard filters, to group these by Standard/ST Code, without the version. | |
We are going to update the provider/employer standards to allow the selection of a proctoring service | |
To make this data visible via the API on new endpoints, to aid with integrations such as Aptem and others going forwards. | |
Rewrite of Contracts, with addition of a base contract for Providers where a contract is not yet set up, this will utilise the base contract and the prices set therein. This base contract can also used as a template, by which other contracts are set up from. | |
Look at being able to archive off apprentice data. |