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 * 9 dev team members (adjusted as below)76.5 days

Paul -1, Yafang -5, JohnO -5, Jay -2, Simon -1, Andy D -1.


Total team availability this Sprint80.3%

POs present a review of Sprint goals and other committed work

Sprint Goal

  1. Release new UI for PPT and support our apprentices to release service status.
  2. UI enhancements to PPT and Auto-rerunning of overnight processes if they fail.
  3. Storing ESR information in a traceable and validated manner.

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 - storing information in a traceable and validated manner










Release new UI for PPT and support our apprentices to release service status







UI enhancements to PPT and Auto-rerunning of overnight processes if they fail







Other

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 (achieved? (thumbs up) / (thumbs down)): 

  1. Release new UI for PPT and support our apprentices to release service status.
  2. UI enhancements to PPT and Auto-rerunning of overnight processes if they fail.
  3. Storing ESR information in a traceable and validated manner.

Next Sprint priorities

  • No labels