Sprint 1 Review (2019-09-17)

Availability (assume Team Availability Calendar is up to date, otherwise, everyone was available for 8.5 days of the 2-week Sprint)

Full team availability 8.5-day Sprint * 9 dev team members (adjusted as below)76.5 days

Ola -3 and Knowledge transfer, Jay -1


Total team availability this Sprint95%

POs present a review of Sprint goals and other committed work

Sprint Goal

POs supported by Dev team provide narrative on why, and what, emergency work was brought into the Sprint and which committed-to tickets were moved out as a result

Live Issues:

type summary story points (effort) assignee created status
Loading...
Refresh

Dev team demo 'done' work contributing to those goals (no more reference to specific list of Jira tickets, and no more reference to work not 'done')

AreaItemDemo - from Prod URL where feasible
ESR

ESR - Date of birth and postcode length exceeding 8 characters and is not accepted by ESR and therefore do no appear on ESR applicant records

DOB Validation — Watch Video

ESR - Applicants being exported in Duplicate - do not need to re-send applicants for positions that have already been exported before - don't create duplicate records

Duplicates — Watch Video

For the bi-directional TIS-ESR Interface - looking at the architecture and design for how to build this

Esr notification daily load stuck for numbers of records (14K) on 4 September 2019
TIS



Service unavailable issue - We have applied a fix so please provide feedback if you still get this issue.
We will do some more investigation and evaluation of the fix applied for this issue reported by the teams community last week


Investigation of Ahead of Time (AOT) compiling of code - this will decrease the loading time of pages in TIS, and add extra levels of security on the app

Completed tasks

  1. AoT test site created for the strategic transitioning of TIS's compilation from Just in Time (JIT) to AoT.
  2. As before, further tests across the test site show a reduction in page loading time by approximately 3 seconds.
  3. Intermittent and random unit test failures due to switch to AoT fixed.


Next Steps

  1. Address issue with Lazy-loading of modules required for TIS.
  2. Address AoT-driven issues with end-to-end (e2e) tests.
  3. Introduce a level of monitoring in Admins-UI so that errors are easily surfaced and identified.
  4. Re-configure deployment pipeline to account for introduction of environment variables which enables us to align/mis-align our environments (Dev/Stage/Production) on demand for strategic testing.

Remove Definer statement in MySQL in TCS - Basically means investigating how to migrate the TIS database to new infrastructure in the future


Find Site and Trust using the "known as" field

Before:

Now:

Removal of erroneous assessment records3277 Assessments marked as deleted using a bulk update to the database


NDW: Add Field to TIS_Interim > CurriculumMembership

Screenshot from SQL-06

Placement Planner

Placement Planner - Full placement is not rendering

Before:

https://www.loom.com/share/7739685ac59a497b8e91d770f4c9c69e

Now:

https://www.loom.com/share/cb9386877a10407eb33c345c387a8c3c

Placement Planner - fix flashing when hovering over site filter


Placement Planner - Be able to create placements without typing the post number


Service Status

Ongoing work by the apprentices for their service status project 


Stakeholders / Users invited to query / interrogate / applaud (after Sprint Review POs convert consensus inputs into backlog tickets, giving the option to consider them in the coming Sprint Planning)

Sprint Goal: .

Next Sprint priorities