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

Simon -5, Andy D -3, Liban -2, Jay -1. 


Total team availability this Sprint86%

POs present a review of Sprint goals and other committed work

Sprint Goal: Improve the efficiency of development to better enable the team to build a better product for our end users.

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.

Add Field to indicate whether trainee is CCT (Certificate of Completion of Training) or CESR (Certificate of Eligibility for Specialist Registration)


2.

Change the person owner rebuild Jenkins job to call an endpoint
Can we re-title this to be descriptive of benefit to the user, please?


3.Coding standards / style


4.

SYNC SERVICE: API Endpoints for each routine and basic web interface to launch them
Can we re-title this to be descriptive of benefit to the user, please?


5.

Bulk Upload for People not updating NI number for existing trainees


6.

As a TIS user I want the application to work quickly through use of Angular AoT

Current State of TIS startup after user login: https://www.loom.com/share/aaf9b808863a4c1e84ad27793bdaa440

Aspirational State of TIS startup after user login: https://www.loom.com/share/b5c6b1020ca041199eb7303e51691cc2

7.

Create a new staging server for testing the Angular AoT Changes whilst still using the staging database, so that we can use real-world data, but are not affecting the normal stage environment/workflow.

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: Respond to user feedback on PPT and data in NDW to make both more usable.

Next Sprint priorities

  • No labels