Welcome
- out loud on the call - really, we’d appreciate you doing this!; |
|---|
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')
Area | Description | Team Representative | Demo - from Prod URL where feasible |
|---|---|---|---|
TISSS | Data syncing from TIS blocked by Curricula marked as deleted | Two curricula exist with a status of “DELETED”, this status was not correctly handled by the TIS → TISSS sync process and caused an error. | |
FormR part B COVID declaration not shown on live environment | The COVID declaration was set up as a toggle-able feature, which unfortunately had not been turned on in the live environment. | ||
FormR Part B - Declaration Type dropdown has no options. |  The values for the dropdown are taken from a set of reference data, the live environment had no values included in our reference data. | ||
FormR Part B - Covid Change Circumstance dropdown has no options. | The values for the dropdown are taken from a set of reference data, the live environment had no values included in our reference data.  | ||
Unable to save or submit forms in live environment | The live application did not have the correct permissions granted to it, it mistakenly had the same permissions as the test environment. This caused save and submit to fail as it tried to access live resource with test permissions. | ||
Specialties now being synced between TIS and TISSS | |||
Form R - Amend date range validation from + or - 10 years to 25 years (e.g. Programme Start date - part A; Type of work Start date - part B) | Live demo | ||
Relabel the Sensitive data heading to Registration details. Instead of GMC, GDC, PH, use the full label or registration body name to make them clearer. | Live demo | ||
Support Query - selectable local office | Live demo | ||
Form R Part B bug fix (Date of Previous Revalidation) | Before  After | ||
TISSS Feedback - "X" (close) button not functioning | Before:  After: (live demo) | ||
Reval | Syncing TIS and GMC data into Reval WIP | Discussion of ongoing work to synchronize TIS and GMC data into Reval (Where we are up to) | |
TIS | Add Sentry Alerting the the NDW-ETL | The NDW-ETL service will now notify the developers and Data/TIS leads once the connections to the databases has been interrupted by way of sending a slack notification through sentry, allowing for quicker and more efficient responses | |
Make sure the Dev team can restart failed jobs | What we’ve done:
|
Objective Key Results (OKRs) Financial Q1
OKR | 1st | 2nd | 3rd | 4th | 5th | 6th |
Objective: Support Trainees with their use of TIS Self-service | ||||||
Key Result#1: No unresolved 'serious' queries (combining # of queries with their nature) | too early | too early | ||||
Key Result#2: Trainees score overall experience and satisfaction of TIS Self-service at 6 or higher | too early | too early | ||||
Key Result#3: 70% of Trainees engage with TIS Self-service as part of the initial pilot | too early | too early | ||||
Key Result#4: Admins surveyed indicate their overall experience and satisfaction is 6 or higher | too early | too early | ||||
...
| Info |
|---|
*TIS Self-service MVP:
HEE Admins:
|
TIS Dev team roadmap:
| Trello card | ||
|---|---|---|
|
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!
...