Sprint 53 Review (2018-07-25)

Availability

(assume Team Availability Calendar is up to date, otherwise, everyone is available for 9 days):

Sprint Priorities

The following list was the prioritisation output from Sprint Planning - largely a stabilisation Sprint:

1. BAU. To include:
   • PO Group to refine priorities in the backlog - Alistair Pringle (Unlicensed), Joanne Watson (Unlicensed), Former user (Deleted), Ashley Ransoo, This is the #1 priority piece of work for the POs during the Sprint.
   • Jayanta and Hamed, supported by John will form a BAU team this Sprint to focus on Bugs.
     - Multiple FundingType per Posts are duplicating Posts in the post list 
     - Placements created have 'disappeared'
     - Placements is allowing users to select Inactive posts Recording Placements
     - TIS has reverted changes made by users (Ophthalmology)
     - Cannot update site of Post when post is linked to a rotation Record Creation (Post)
     - TIS_NDW ETL error handling is looping and filling logs
     - Changes to rotation are not reflected in ProgrammeMembership Record Programme Memberships
     - Training Descriptions not displayed in Placements Recording Placements
     - Duplicate Main Site / Approved Grade / Primary Specialty created when editing a post with auto-generate NPN set
   • Help devops on the env alignment for the anonymiser
     You may not have all the skills and knowledge to handle all the priority Bugs, but this is a great way of:
     1. getting exposure to the widest degree of the codebase / infrastructure
     2. pair with other members of the team who have the knowledge / skills needed
     3. instigate knowledge transfer sessions when encountering an area of the codebase / infrastructure with which there is unfamiliarity
     4. encouraging liaison with the PO Group in order to confirm business value for each Bug and the extent (speed of turnaround, breadth of solution required, longevity for the solution, etc) needed
2. Technical debt +
   • Each functional group - FED, BED, Ops, Everyone else (I do not want to discount others in the team), to determine their top 'n' number of high priority tech debt, size it, allocate it, and timebox days in the Sprint to address it. Come to Stand up on Monday morning with that list to socialise what you are doing and when you are doing it, so where there might be knock on impacts on others, they have the right to feed in. Particular attention to supporting Shivani with addressing the test strategy.
3. Knowledge transfer (assessment of what's left - who could feasibly do this?)
   • Confluence housekeeping - especially deleting documentation that is out of date. Ongoing
   • Dev standards (Dev meeting / series of meetings). Ongoing
   • Pairing / Mobbing
   • Git-commit messages
   • Walk-throughs (prep as you go - links?). 
   • Architectural level diagrams (Reuben leading - update?)
4. Development (P1s - POs to review what are P1s in Jira as a matter of urgency)
   1. Document management - accessing existing documents (better dataset to work from, but work needed to be done on reviewing metadata before dev work should commence), and creating, updates and deletes of new ones (easier to achieve). Chris / Luis
   2. Placement comments - Update please?
   3. Removal of deleted records - records marked as "Delete" in DR2, but brought over to TIS as "Current"
   4. NDW UAT missing data analysis - Fields that don't exist in TIS that NDW want in TIS. And fields that don't exist in NDW but do exist in TIS.
   5. ESR - Assisting ESR / NDW with live ESR issue - TISDEV-5089 - GMC/GDC issue, TISDEV-5081 - firstnames/middleName issue & TISDEV-5062
   6. New Listing component
5. Non Dev (PO & BA)
   1. NDW - analysis to finish off - How to delete going forward (Ify)
6. Ops
   
   1. restrain the DB / productionising the DB
   2. Deployment pipeline
7. Testing
   1. E2E automation pipeline
   2. E2E regression pack stablisation
   3. Relese Testing

Contents

The following items to be shared by team members during this sprint review