Welcome
|
|---|
Live Issues:
| Incident logs 2020-12-23 Bulk Upload Survey Error - Outcomes 2020-12-13 Reval Legacy/Old GMC Sync - GMC return code 98, GMC internal error |
|---|
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 |
|---|---|---|---|
TIS Team | Sprint Goal: Continue the process of NI Data migration | ||
Northern Ireland Instance/Setup | |||
Revalidation Team | Sprint Goal: As a reval admin, I can view connection history and hidden trainees | ||
Displaying programmes and connection historyView Hidden Trainee Records in Summary View | |||
Cannot link out to other areas of TIS from Trainee record | |||
View Hidden Trainee Records in Summary View |
Objective Key Results (OKRs) Financial Q3
Scores | |||||||
TIS Squad | 1st | 2nd | 3rd | 4th | 5th | 6th | |
Objective | Technical facilitation of the on-boarding of new entities (beginning with NIMDTA this quarter, and to be followed in future by HCS, Pharmacy, and others) | ||||||
Key Results | NIMDTA admins administer their Trainees via TIS / a NIMDTA instance of TIS | too early | 0.1 | 0.5 | 0.6 | 0.7 | 0.9 |
Data between England and NIMDTA instances of TIS is digitally synced such that administrators from each entity are able to attach Trainees from the other entities to their Programmes | too early | 0.1 | 0.2 | 0.2 | 0.2 | 0.3 | |
Revalidation Squad | 1st | 2nd | 3rd | 4th | 5th | 6th | |
Objective | Replace the Existing Revalidation Module with new Revalidation Module | ||||||
Key Results | A new live/production environment built with a supported connection to GMC | too early | too early | 0.7 | 0.9 | 0.9 | 1.0 |
Trainees can be revalidated, their connections can be managed and concerns can be logged | too early | too early | 0.3 | 0.6 | 0.6 | 0.7 | |
Ensure users can view existing TIS reval data | too early | too early | 0.0 | 0.2 | 0.2 | 0.2 | |
...
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! Your contributions to this survey are entirely anonymous, should you wish to include anything others might perceive as controversial. We welcome any and all feedback, as long as it is constructive!
...