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 Sprint | 86% |
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:
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
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') |
|---|
| Item | Demo - from Prod URL where feasible | Demo link |
|---|---|---|
1. | Add Field to indicate whether trainee is CCT (Certificate of Completion of Training) or CESR (Certificate of Eligibility for Specialist Registration) | Creating and Editing Programme memberships with new Training pathway field: https://www.loom.com/share/4646e0602ebd496aa02ede287dd2e7b7 |
| 2. | Change the person owner rebuild Jenkins job to call an endpoint | |
| 3. | Coding standards / style | |
| 4. | SYNC SERVICE: API Endpoints for each routine and basic web interface to launch them | Sync service is a backend service which repopulates the connection among database tables and creates new data records in database and ElasticSearch. Then other services or frontend can use these data directly. There are 6 jobs in Sync service now. All of them are launched daily at midnight. But sometimes they are needed to be launched manually due to some exceptions. This ticket is for providing our developers with a webpage to trigger these jobs individually or sequentially just by clicking buttons so that we can launch them in an easier and more efficient way. |
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. |
|
| 8. | System Status - Abrar and Pete Project | Update on what to build - decided scope |
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. |
|---|
POs present the roadmap: https://ext.prodpad.com/ext/roadmap/d8a231e0ec66a7a9ead4f1464ab24fca5b816dbf |
|---|
Next Sprint priorities |
|---|