Page Comparison

PO present a review of Sprint goals and other committed work

Sprint Goal:

Make placements that have been approved editable, so that users can fix any mistakes themselves
Handle Position deletion for applicant process and increase robustness to data changes
Creating a database to store Trainee app data
Continue getting TIS ready for the recording and generating of NTN

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

server	System JIRA
columns	type,summary,story points (effort),assignee,created,status
maximumIssues	20
jqlQuery	project = TISNEW AND issuetype in (LiveDefect, Support) AND Sprint = 271 order by created DESC
serverId	4c843cd5-e5a9-329d-ae88-66091fcfe3c7

Sprint Challenges

On the x day of Christmas, the TIS team brought to me		Item	Demo - from Prod URL where feasible
Day	Area	Item	Demo - from Prod URL where feasible
1	Bulk Upload	When I upload a Programme Membership, then the training pathway defaults to 'CCT' or 'N/A'.
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
5
6
7
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)

Make placements that have been approved editable, so that users can fix any mistakes themselves
Handle Position deletion for applicant process and increase robustness to data changes
Creating a database to store Trainee app data
Continue getting TIS ready for the recording and generating of NTN

- Overall and next sprint

Versions Compared