Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

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 members60 days
Andy, Yafang, JohnO, Simon, Ola, Jay, Pepe, John


Total team availability this Sprint95%

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
  1. Person Owner incorrect based on current Programme membership
  2. Programme role for Placement Planner users

Additional committed work:

  1. Bulk Update Posts using TIS_Post_IDs (Rotations)

  2. Add 'other sites' field to the placement

  3. ESR ETL Notification date coverage

  4. Remove the Synchronisation jobs within TCS and build a separate Synchronisation service
  5. 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:

  1. Lynn NE User Permissions

  2. ESR - First Wednesday of August - A large number of placements' commencing and notification-daily-load is not able to cope

  3. Person Placement Employing and Training Body trust jobs failing

  4. 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')

ItemDemo - from Prod URL were feasible

1.

Live demo of attributes of a user that has been assigned the newly created HEE Programme Admin role

2.

Demo of post rotations bulk update.
3.


4.


5.
6.


7.
8.Add other sites to Placments - NDW data export (PlacementOtherSite) Jayanta Saha
9.

Lynn NE User Permissions Jayanta Saha

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

  • No labels