Welcome
Overviews of the iteration Any interruptions / Live Defects Team going through what they’ve achieved during the iteration Feedback from those on the call on what we have done (constructive criticism / praise / questions) Collaboration with those on the call on what to do next Ask questions:
- out loud on the call - really, we’d appreciate you doing this!;
- write in the Team meeting chat; or
- fill in the post-Review survey after the call
(for questions that occur after the call is over, or if you don’t want to ask the question during the call for whatever reason, and
for letting us know whether the Review meets your expectations, or whether you have some suggestions for improvement) |
|---|
Live Issues:
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| columns | key,summary,created,updated,status |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = TIS21 AND issuetype = LiveDefect AND status in (Backlog, "Being code reviewed", "Check ACs", Documentation, Done, Implementing, "Measure of success", "Ready for development", Refinement, "Released to Prod", "Released to Stage", "Tests/Logs/Monitoring", "Verifying on Prod", "Verifying on Stage") AND created >= 2021-03-16 AND created <= 2021-03-30 order by created DESC |
|---|
| serverId | 4c843cd5-e5a9-329d-ae88-66091fcfe3c7 |
|---|
|
| Incident logs 2021-03-22 Over-logging of some services 2021-03-22 ESR message queue failure 2021-03-18 Not able to create new trainees in TIS 2021-03-18 Bulk Upload failures 2021-03-16 ESR APP generation and TIS sync job failures |
|---|
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 |
|---|
TIS | workEmail removed from person view in NDW
| Andy Dingley | |
Make Employing and Training bodies mandatory on Post | Edward Barclay | |
Reval | Visitor trainee populate from TIS to Reval with RabbitMQ and Elastic Search | Doris.Wong | Live demo: Pragramme membership saved in TIS to trigger trainee add/remove in Exception list  Image Modified |
| | |
ESR | | | |
| | |
TIS SS | Certain users unable to create FormR A/B | Andy Dingley | If a trainee’s latest programme had no medical curriculum then a FormR A/B could not be created, instead a “spinner” was shown indefinitely.  Image Modified
In this scenario the form is now created as expected, with pre-populated fields that take data from the curriculum left blank.
|
Populate programme memberships | Reuben Roberts | Trainee’s programme memberships and curricula are now sync’ed across from TIS:
From TIS:  Image ModifiedTo TIS-SS:  Image Modified |
Support query page | john o | Demo from prod |
Objective Key Results (OKRs) Financial Q4
| 1st
Iteration | 2nd
Iteration | 3rd
Iteration | 4th
Iteration | 5th
Iteration | 6th
Iteration |
Objective#1 | Trainees can access the TIS Self-service app, see their details and be able to fill in their Form Rs, and HEE admins can unlock / un-submit any Form Rs that are submitted from within the TIS app
(i.e. Complete the MVP* for TIS Self-service) |
Key Results | | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 | 0.1 |
| 0.1 | 0.1 | 0.2 | 0.2 | 0.2 | 0.2 |
| 0.5 | 0.6 | 0.6 | 0.6 | 0.8 | 0.9 |
| 0.6 | 0.6 | 0.6 | 0.7 | 0.7 | 0.9 |
...
| Info |
|---|
*TIS Self-service MVP:
Trainees: have a login to TISSS and know what to use it for, and can reset their passwords can access their personal details held on TIS can see their current and future Programme and curriculum membership they are training on can ensure placement details are accurate and have a way of knowing where they are going to be training next have visibility of their assessments including upcoming ones are able to complete their Form R Parts A and B electronically are able to receive support when they have queries regarding using Trainee Self Service or Submitting specific forms
HEE Admins: |
TIS Dev team roadmap:
| Trello card |
|---|
| url | https://trello.com/b/I2KstFzF/tis-interim-roadmap?menu=filter&filter=label:TIS%20Self-service |
|---|
|
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!