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



Total team availability this Sprint????

POs present a review of Sprint goals and other committed work

Sprint Goal

  1. Set up Trainee UI infrastructure and integrate CurriculumGMCreference into TIS and NDW.
  2. Create an AWS SFTP server and set up auditing for records and messages.
  3. Continued improvement with Placement Planner.

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

AreaItemDemo - from Prod URL where feasible

Placement Planner continued improvements

  1. Maximise planner space i.e. each placement of a given post to be on the same line unless they are in a shared date slot.
  2. For ‘small length’ placements, display just the placement type (circle). The other placement details are displayed via a tooltip.
  3. Fix a timeline months bug whereby choosing a PPT 'Date From' (e.g. 31/10) where the next month has less days (e.g. Nov has 30 days) will result in incorrect timeline months being displayed (this fix was found during this sprint when working on the above two tasks).
  1. & 2. Maximise planner space & Displaying 'small length' placements

Before: https://www.loom.com/share/1218a8705c8446aeb579d4f3a287bdd5

3. Timeline bug

Before: https://www.loom.com/share/424587abfa9a4c64809c81ce45e1c0ed 


After (1, 2 & 3)

https://www.loom.com/share/d5c38dbbb7a543ab886834bf821945df








AWS CognitoUser authentication service for Trainee UI













Assessment and People

Removed redundant fields

  1. Removed columns from Bulk Upload template for Assessment
    1.1 Status (column F), Portfolio Review Date (column K), Trainee Notified of Outcome (column X)

  2. Removed input fields from Frontend
    2.1 People - Sensitive Data - Inactive notes
    2.2 People - Qualification - Month attained, Year attained
    2.3 People - Person Details - College

  3. Removed options from dropdown menu (changed status into 'INACTIVE' in the database)
    3.1 Assessment - Type - RITA
    3.2 People - Programmer membership type - FTSTA, LAT

Before:

1.1

2.1


2.2

2.3

3.1

3.2


After:

1.1 
2.1 https://apps.tis.nhs.uk/admin/people/person/2/edit-sensitive-data
2.2 https://apps.tis.nhs.uk/admin/people/person/2/edit-qualifications
2.3 https://apps.tis.nhs.uk/admin/people/person/2/edit-personal-details
3.1 https://apps.tis.nhs.uk/admin/assessment/12658/assessments/923892
3.2 https://apps.tis.nhs.uk/admin/people/person/2/edit-programme

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)

Sprint Goal (achieved? (thumbs up) / (thumbs down)): 

  1. Set up Trainee UI infrastructure and integrate CurriculumGMCreference into TIS and NDW.
  2. Create an AWS SFTP server and set up auditing for records and messages.
  3. Continued improvement with Placement Planner.

Next Sprint priorities

  • No labels