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 8.5 days of the 2-week Sprint)

Full team availability 8.5-day Sprint * 8 dev team members68 days
Andy, Yafang, JohnO, Simon, Ola, Jay, Pepe, John


Total team availability this Sprint??%

POs present a review of Sprint goals and other committed work

Sprint Goal: 
Complete sync service and focus on a Revalidation workshop - to determine the plan of attack.
  • Note there was no subsidiary work this Sprint - as we are using 'Themed' Sprints now, 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 where feasibleDemo link

1.

TIS-ADMINS-UI: Security vulnerabilities (Ola and JohnO)


2.

Changing the trust a Site is linked to on the Site reference table on the FE does not cause the Trust ID to be updated (??)


3.

Reval (& Concerns and Notifications) rebuild architecture workshop (Alistair)


4.

Replace backend query param sanitizer (??)


5.

Remove the Synchronisation jobs within TCS and build a separate Synchronisation service (??)


6.ESR - Investigate on having Monitoring for the FTP uploads and downloads failures on N3 (??)
7.Portsmouth NHS Trust applicants for August 2019 Rotations not exported (??)
8.Support Traffic Light and Summary Page (Apprentices)

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