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 3 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 members (adjusted as below)68 days

Yafang, Ola, Pepe,
Simon -1, JohnO -2.5,
Andy -4,
John -7.5(?), Jay -9


Total team availability this Sprint65%

POs present a review of Sprint goals and other committed work

Sprint Goal: Addressing user feedback as front end navigational enhancements on the Placement Planning Tool.
Plus other committed-to work:
  • ESR-ETL : Fix the code in NotificationProcessor when notification-daily-load is triggered
  • Upgrade Angular from 5.2 to version 6
  • Admin Page (Service status)

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.

Placement Planning Tool throwing error for some programmes - Missing mandatory fields on Placements

https://www.loom.com/share/6b96487acc3f49ba838d82e361719d49
2.

Extend logic for Programme role for Placement Planner users


3.

NPN to be visible when navigating across the dates in a plan.


4.

Partial placement display where a placement straddles the date range searched.


5.

Define criteria before rendering the plan


6.

ESR-ETL : Fix the code in NotificationProcessor when notification-daily-load is triggered


7.

Upgrade Angular from 5.2 to version 6


8.

Admin Page (Service status)





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)

Review Sprint Goal: Addressing user feedback as front end navigational enhancements on the Placement Planning Tool.

Next Sprint priorities

  • No labels