Welcome
|
---|
Live Issues:
| Incident logs |
---|
Dev team demo 'done' work contributing to those goals (no reference to specific Jira tickets, and no reference to work not 'done')
Squad | Area | Team Representative | Demo - from Prod URL where feasible | ||||
---|---|---|---|---|---|---|---|
ESR: | Goal: Update applicant record on placement date change | ||||||
ESR Applications error monitoring dashboard | https://sentry.io/organizations/health-education-england-9v/projects/ | ||||||
Send DiT Grades to ESR | |||||||
Investigate trainees not having app files due to be transferred on 6th of May 2020 | ESR MedRot rows to check:
| ||||||
TIS / TIS Self-service: | Goal: Complete the save function in Form R and investigate how to add the Covid section as a modular section of the Form R | ||||||
Save function in Form R Part B | Live demo | ||||||
Fix the bug that some placements can not be updated or deleted | |||||||
Uptime MonitoringPhil but happy for someone else to take the glory - I reckon ops should do it lol | |||||||
Revalidation: | AS a reval admin, I can upload and remove documents in concerns | ||||||
| |||||||
AWS Migration: | Introduction |
|
Objective Key Results (OKRs) Financial Q2
TIS Self Service | Revalidation | ESR Bi-Directional Project | AWS Migration | |||||||
Obj. | Be ready to switch on TIS Self-service, should the business give the green light | Obj. | Concerns logging and connections summary | Obj. | Move ESR Single directional to new world code and be ready to remove restrictions on Bi-Di when the business gives the green light | Obj. | Lift and Shift to our new hosting home (Amazon Web Services) | |||
Key R | Data synced between TIS and TIS SS (AWS) | Key R | View connections status by trainee | Key R | Files sent to ESR from new codebase, and Remove reliance on N3 completely | Key R | Seamless transition with no downtime | |||
Submitted Form Rs can be processed digitally by Admins | TIS Admin can assign reval roles | Provide accurate reports to Trusts / Regions for files we have exported. Remove reliance on N3 completely | Perform a stress test to get a benchmark after migration | |||||||
Users have accounts and can access only their data | Ability to raise and manage a concern | Time spent investigating and resolving any issues is reduced (LiveDefects and 'blind spots'). [Sentiment scores? Resolution time? RCA steps? Something else?] | TCS, Admins UI, TIS Self Service, Revalidation all running on AWS production environments | |||||||
Able to pilot TIS SS | Able to upload and download concerns documents | We identify 100% of issues in advance of being informed by Trusts | Refactoring some apps to migrate to new blob storage | |||||||
Score | Score | Score | Score |
Feedback
We really do welcome any feedback you have for us - whether it be negative or positive, or whether it be a suggestion of something we could try/incorporate in a future Sprint Review. We absolutely don’t want to stand still. We’re very happy applying the 12th Agile principle of ‘becoming more productive’ to our Sprint Reviews themselves! Here’s a selection of feedback received so far, from previous Sprint Reviews.
...