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

Version 1 Next »

Availability (assume Team Availability Calendar is up to date, otherwise, everyone was available for 7.5 days (this Sprint includes a Bank Holiday) of the 2-week Sprint)

Full team availability 7.5-day Sprint * 9 dev team members (adjusted as below)67.5 days

Ola -Knowledge transfer


Total team availability this Sprint77%

POs present a review of Sprint goals and other committed work

Opps we forgot

Sprint Goal: Improve HEE Admin users ability to manage PostFunding more accurately for financial reporting, and ensuring NDW allows users to interrogate up to date data.

Other committed-to work in the Sprint:

  • We need to move our databases to be managed by our hosting provider (to ensure greater resiliency). To do this we need to modify them (all) slightly first.
  • To indicate which placements are whole time equivalents on the summary screen, rather than force users to drill down to find out this information.
  • Team to assess outputs from the Trainee workshops, to determine what work should be carried out to get us to an MVP.
  • Introduce validation to prevent users from accidentally deleting a curriculum on a trainee record.
  • Work remaining from last Sprint: For those services that don't auto-restart, create an interface for any member of the team to restart any service that fails at any time of day in order to get that service back up and running as quickly as possible for users.

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:

type summary story points (effort) assignee created status
Loading...
Refresh

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

AreaItemDemo - from Prod URL where feasible
ESR

ESR - Date of birth and postcode length exceeding 8 characters and is not accepted by ESR and therefore do no appear on ESR applicant records


ESR - Applicants being exported in Duplicate - do not need to re-send applicants for positions that have already been exported before - don't create duplicate records


For the bi-directional TIS-ESR Interface - looking at the architecture and design for how to build this


TIS



Service unavailable issue - We have applied a fix so please provide feedback if you still get this issue. We will do some more investigation and evaluation of the fix applied for this issue reported by the teams community last week


Investigation of Ahead of Time (AOT) compiling of code - this will decrease the loading time of pages in TIS


Remove Definer statement in MySQL in TCS (and *TEST*) - Basically means investigating how to migrate the TIS database to new infrastructure in the future


Find reference data (Site, Trust etc) using the "known as" field 


Removal of erroneous assessment records

Placement Planner

Placement Planner - Full placement is not rendering


Placement Planner - fix flashing when hovering over site filter


Placement Planner - Be able to create placements without typing the post number


Service Status

Ongoing work by the apprentices for their service status project 


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: Improve HEE Admin users ability to manage PostFunding more accurately for financial reporting, and ensuring NDW allows users to interrogate up to date data.

Next Sprint priorities

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.