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 12
Next »
POs present a review of Sprint goals and other committed work |
|---|
Sprint Goal: - As an HEE-Admin, I can approve draft placements.
- Produce csv APP file for ESR consumption and including position deletions
- Getting TIS ready for the recording and generating of NTN
- Evaluating Core React Libraries and coming up with the useful ones to build Trainee UI
- Complete Angular Upgrade so that TIS UI is running on a recommended/stable version of Angular |
|---|
POs supported by Dev team provide a 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') |
|---|
| Area | Item | Demo - from Prod URL where feasible |
|---|
ESR Write generated App records to file and upload | AWS Lambda - allows new system to be eventful Generation of APP files Upload of APP files to AWS Update File Splitter Service to work with AWS
| 
Where we were as of the Sprint 5
Where we are now at the end of Sprint 6
Demo
|
Training Pathway - automatically set by default based on curriculum selection on Programme membership.
TISNEW-3389
-
Getting issue details...
STATUS
| - If Curriculum leads To CCT, then default Training Pathway to CCT
- If Curriculum does not lead to CCT, then default Training Pathway to N/A
- If at least one of the curricula attached Leads to CCT (where there are multiple), then default Training Pathway to CCT when creating/updating programme membership
- Exception: If Training Pathway was set to CESR: Keep as CESR when adding/changing curricula, but this can be manually overridden
- In any of the cases, you are able to override the default value on update/create journeys.
- If a user updates the LeadsToCCT value in the curriculum reference, then no action retroactively on existing prog. memberships.
| Demo on stage |
| Placement | - Added 'Approve All' button to PPT for approving all placements in the programme
- Added the 'Approval' field in the placement create/ update page
NOTE: Draft placements will have a red border in the PPT.
Approved users (e.g. HEE Admin) - Add 'approve all placements button' and confirmation modal popup for approved users
- Display drop-down menu (with options: APPROVED, DRAFT) for DRAFT placements
- Disable the Approval field for APPROVED placements but allow other fields to be updated*
- The new placements created with the bulk-upload function will be set as 'Approved'
Unapproved users - Lock Approval field for non-approved users but allow them to update other fields on DRAFT placement.
- Remove the 'update' button for non-approved users for placements that have been APPROVED
| Live demo |
|
|
|
|
|
|
|
|
|
|
|
|
| NDW | Add LeadsToCCT field to NDW within VwCurriculum |
|
| Trainee's App | Identify Core Libraries - The framework/building materials for the visible part of the application. | We identified a set of libraries that we'll use for building the user interface, either, straight-away or very soon after starting. As part of the conversation it was clear that we would end up needing to spend some time evaluating how well these libraries fit what we are developing, including changes to our understanding of what Doctors in Training want to see. |
|
|
|
|
|
|
Sprint Goal (achieved?  /  ): - As an HEE-Admin, I can approve draft placements.
- Produce csv APP file for ESR consumption and including position deletions
- Getting TIS ready for the recording and generating of NTN
- Evaluating Core React Libraries and coming up with the useful ones to build Trainee UI
- Complete Angular Upgrade so that TIS UI is running on a recommended/stable version of Angular |
|---|
Current Priorities- Overall and next sprint
|
|---|
0 Comments