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 9
Next »
Availability (assume Team Availability Calendar is up to date, otherwise, everyone was available for 7.5 days (this Sprint includes a Bank Holiday) of the 2-week Sprint)
| Full team availability 7.5-day Sprint * 9 dev team members (adjusted as below) | 67.5 days |
|---|
Pepe -5, Jay -1, Simon -2, Ola -Knowledge transfer |
|
| Total team availability this Sprint | 77% |
|---|
POs present a review of Sprint goals and other committed work |
|---|
Sprint Goal: Improve HEE Admin users ability to manage PostFunding more accurately for financial reporting, and ensuring NDW allows users to interrogate up to date data.
|
|---|
Other committed-to work in the Sprint: - We need to move our databases to be managed by our hosting provider (to ensure greater resiliency). To do this we need to modify them (all) slightly first.
- To indicate which placements are whole time equivalents on the summary screen, rather than force users to drill down to find out this information.
- Team to assess outputs from the Trainee workshops, to determine what work should be carried out to get us to an MVP.
- Introduce validation to prevent users from accidentally deleting a curriculum on a trainee record.
- Work remaining from last Sprint: For those services that don't auto-restart, create an interface for any member of the team to restart any service that fails at any time of day in order to get that service back up and running as quickly as possible for 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 |
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 |
|---|
Ensure that the funding body data is passed over to the NDW each day. | NDW ETL is the piece of code which runs everynight 12:20 am to export TIS data to NDW data warehouse so that report can be generated. The user requirements were to export the data of FundingbodyId field of PostFunding table and newly introduced TrainingPathway field of ProgrammeMembership to the NDW. Those were exposed to NDW through the NDW ETL. NDW Team have confirmed those fields are in Prod. |
Work remaining from last Sprint:
Ensure that the training pathway field is included in the data passed over to the NDW each day. | As above |
| Give HEE Admins the ability to bulk update Posts Funding details as an efficient way of managing existing Post Fundings in bulk. |
|
We need to move our databases to be managed by our hosting provider (to ensure greater resiliency).
To do this we need to modify them (all) slightly first. |
|
| To indicate which placements are whole time equivalents on the summary screen, rather than force users to drill down to find out this information. | Loom video for demo: https://www.loom.com/share/6eac79d353b943b88cb2f5cb9e7c0eae |
| Team to assess outputs from the Trainee workshops, to determine what work should be carried out to get us to an MVP. |
|
| Introduce validation to prevent users from accidentally deleting a curriculum on a trainee record. |
|
Work remaining from last Sprint:
For those services that don't auto-restart, create an interface for any member of the team to restart any service that fails at any time of day in order to get that service back up and running as quickly as possible for users. |
|
Sprint Goal: Improve HEE Admin users ability to manage PostFunding more accurately for financial reporting, and ensuring NDW allows users to interrogate up to date data. |
|---|
0 Comments