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 |
---|---|
JohnO -7, Yafang -5, Andy D -2, Simon -1, John S -1 | |
Total team availability this Sprint | 76% |
POs present a review of Sprint goals and other committed work |
---|
Sprint Goal: Respond to user feedback on PPT and data in NDW to make both more usable. | |
---|---|
Plus other committed-to work:
|
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 |
---|
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 UserProgramme table to daily NDW export | Jay ?: |
2. | When searching in Programmes for a Programme only allow users to see Programme that they have access to via their user role. | Yafang ?: |
3. | PPT - Planner does not render the full duration of a Placement if there is only one placement on display | PPT with Bug: PPT with fix applied: |
4. | Implementing agreed coding standards / style | Simon / Andy D ?: (focus on benefits - longer term investment - new developers coming in etc) |
5. | Prevent more than one RO per Local Office for Reval | Pepe: Previously: Now: |
6. | SYNC SERVICE: add logic to sync service to check for failed jobs and rerun when necessary and alert to slack | John ?: (focus on user benefits - fewer overnight issues - reliability of data first thing in the morning etc) |
7. | Upgrade Angular from 5.2 to version 6 | Noteworthy points for upgrade:
|
8. | Develop a common understanding of "What is Angular AoT" | Performance Metrics: What does it mean when we say we want TIS to be fast?
Current Implementation: Aspirational Implementation: |
9. | End to end test failing (both locally and in Jenkins) due to an auto-update of chrome version |
|
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 |
---|
Non Tech Link: https://ext.prodpad.com/ext/roadmap/58c41bcc06a77c08acc891aed47aca7210fdfe03
Next Sprint priorities |
---|
0 Comments