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



Total team availability this Sprint????

POs present a review of Sprint goals and other committed work

Sprint Goal

  1. Set up Trainee UI infrastructure and integrate CurriculumGMCreference into TIS and NDW.
  2. Create an AWS SFTP server and set up auditing for records and messages.
  3. Continued improvement with Placement Planner.

POs supported by Dev team provide a 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

























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. Set up Trainee UI infrastructure and integrate CurriculumGMCreference into TIS and NDW.
  2. Create an AWS SFTP server and set up auditing for records and messages.
  3. Continued improvement with Placement Planner.

Next Sprint priorities

  • No labels