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 25 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 Sprint79%

POs present a review of Sprint goals and other committed work

Sprint Goal: 
Major improvements to ESR
  • Note there was no subsidiary work this Sprint - it was our first 'Themed' Sprint, enabling the whole team to focus their efforts on one specific part of the codebase.

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

ItemDemo - from Prod URL were feasibleDemo link

1.

Users cannot search or filter on all trainees at their local office - Oladimeji Onalaja (Unlicensed)


TISNEW-2993 - Getting issue details... STATUS

2019-05-17 Users cannot search or filter on all trainees at their local office

2.

ESR - performance (SQL refactor) - Joseph (Pepe) Kelly
3.

ESR - No APP Files generated by the TIS-ESR ETL Oladimeji Onalaja (Unlicensed)


4.

ESR - Investigation on handling multiple applicants per deanery number in the DNF/C Files Jayanta Saha


5.

ESR - Daily Notifications Load for Large Numbers


6.

ESR - ETL Notification date coverage


7.TIS-ADMINS-UI - Security vulnerability Oladimeji Onalaja (Unlicensed)
8.ESR Applicant Export Failure 21st May 5pm Joseph (Pepe) Kelly
9.Sync Service

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

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.