PO present a review of Sprint goals and other committed work |
|---|
Sprint Goal:
|
|---|
POs supported by Dev team provide a 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:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Sprint Challenges |
|---|
| On the x day of Christmas, the TIS team brought to me | Item | Demo - from Prod URL where feasible | |
|---|---|---|---|
| Day | Area | ||
| 1 | Bulk Upload | When I upload a Programme Membership, then the training pathway defaults to 'CCT' or 'N/A'. | Joseph (Pepe) Kelly to demo. Old behaviour: |
| 2 | TCS | One off script to generate the Training Pathways on existing Programme memberships based on defined rules | One off script has been written by following these business logic given below- If Leads To CCT = True , then default Training Pathway to CCT If Leads to CCT = False, then default Training Pathway to N/A If at least one of the curricula attached has a Leads to CCT = True where there are multiple curriculum against the Prog. Memb, then default Training Pathway to CCT when creating a new programme membership, when the Training Pathway was previously 'N/A' but has since been updated with an additional curricula which leads to CCT Exception to CESR is: if an existing programme membership with Training Pathway already set to CESR is being updated with a curricula, it should remain as untouched, i.e. keep as CESR. |
| 3 | Trainee-UI | Create database for trainee ui | https://www.loom.com/share/01241a6b51014ca7ad6fc5bb39536573 |
| 4 | Admins-UI | Fixed the page load issue with selection of post -"OOP/CST/Imperial" due to the large number of sites associated with the post. while creating a new placement | Demo |
| 5 | Admins-UI | Technology upgrade - Updated Angular to use LTS(7.2.15) version. | |
| 6 | Trainee-UI | Investigate Microservices and Messaging | Technical discussion and investigation to look at:
|
| 7 | ESR | New developer on board - Say hello Sachin Migration work for LDN New subsystem implemented in TIS to catch data changes to feed into ESR - This helps with the unhappy path during reconciliation Work started on the Deletion flow | Where we were at the end of last sprint:
What the plan is at the end of last sprint:
Where we are now:
|
| 8 | |||
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 (achieved? |
|---|
/ 
)Current Priorities- Overall and next sprint |
|---|