Availability
(assume Team Availability Calendar is up to date, otherwise, everyone was available for 7.5 days (1 Bank holiday) of the 2-week Sprint)
| Full team availability 7.5-day Sprint * 8 dev team members | 60 days |
|---|---|
| Andy, Yafang, JohnO, Simon, Ola, Jay, Pepe, John | |
| Total team availability this Sprint | 95% |
POs present a review of Sprint goals and other committed work |
|---|
| Sprint Goal and associated work: | |
|---|---|
As a TIS user I want to have fewer issues with trainees being unavailable when I am searching So that I can be confident I am seeing all the trainees expected |
|
Additional committed work:
Bulk Update Posts using TIS_Post_IDs (Rotations)
Add 'other sites' field to the placement
ESR ETL Notification date coverage
- Remove the Synchronisation jobs within TCS and build a separate Synchronisation service
- TIS-ADMINS-UI: Security vulnerability: tar
POs supported by Dev team provide 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:
Lynn NE User Permissions
ESR - First Wednesday of August - A large number of placements' commencing and notification-daily-load is not able to cope
Person Placement Employing and Training Body trust jobs failing
Missing reval data
Dev team demo 'done' work contributing to those goals (no more reference to specific list of Jira tickets, and no more reference to work not 'done') |
|---|
| Item | Demo - from Prod URL were feasible |
|---|---|
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) |
|---|
POs present the roadmap |
|---|
Add Comment