Sprint 50 Review (2018-06-13)

Production Application releases / updates

https://hee-tis.atlassian.net/projects/TISDEV/versions/12543/tab/release-report-all-issues

TIS-48 This was a non-user-facing release which disabled the use of special characters in the sanitiser over the weekend. It then enabled the characters on Monday 11th June. Also included additional permissions for the HEE Admin Revalidation role. No notes released to users.

Jayanta

• Confident enough both mentally and technically to do releases.
• Started shrinking the knowledge gap on ESR and JVM Memory management with Jag and Paul.
• Fixed the ticket TIS-915 which was a spelling error of 'known as'.

Matt (UX/UI)

• IA (Information Architecture/Sitemap: TIS Admin IA (Information Architecture) and Site Map
• Sketch prototype: UI, User journeys, user interactions
• Trust admin users: UX: TIS Admin UI - UX Enhancement - Trust admin users
• Programme placements and planner: TIS Admin UI - UX Enhancement - Programme placements (Details, Placements & Planner)
• HEE Posters for TIS Collaborating with Liz.

Sunil 

• Audit the deleted record on all endpoints which delete
• Post reverting to Current after being made inactive
• ETL to support existing Funding information against posts
• Other specialties on some Posts aren't showing on FE
• Assist UAT testing on Reference data
• User cannot delete a programme from a trainee record
• TIS does not allow for searching on posts with a + or brackets

Technical debt

1. Need a cultural change to taking on work (Andy and Simon to lead on coordinating steps to achieve this)
2. Doing work includes: the code, tests (automated), documentation, walk-throughs, design diagrams where necessary
3. Codified DOD (Ways of working)
4. MySQL monitoring

1. Andy Nash (Unlicensed) / Simon Meredith (Unlicensed)
2. All Dev team
3. Former user (Deleted) / PO group
4. John Simmons (Deactivated)

1. Been detailing where the major pain points are:
   -our focus is almost exclusively in writing code and unit tests
   -we need, in addition up-to-date documentation (architectural diagrams: infrastructure, app, data model in particular), clean straightforward and semi-automated pipeline, breadth and depth of testing and everyone being a little more attentive to creating self-documenting code for easier handover
2. Created a new Jira project that we will move over to shortly (need to test moving existing tickets over, and then decide which ones need moving and what needs creating afresh)
3. Ify and the PO group have begun sketching out the overall process in Confluence. Need to ensure that in the new Jira project, where Stories are at the core, sub-tasks are consistently created for the creation of unit and functional tests, updating reference documents (like architectural diagrams, data models) when these get affected etcme
4. Configuration and deployment to dev initially of the MySQL monitoring to see if there are any pain points and to see a historical overview of database and server performance.
5. Sanitiser - was being used to prevent SQL injection when it should really be for business rules. Now looking at prepared statements and a proper search solution
6. Made progress on a strategy for testing

1. -
2. New Jira project
3. Work started in Confluence

1. -
2. -
3. -
4. https://www.useloom.com/share/f541c999831a41b5b693c9eac2f8182b

Knowledge transfer

1. Confluence housekeeping - especially deleting documentation that is out of date
2. Coding standards (workshop?). Javadocs? Or clean coding standards?
3. Pairing / Mobbing
4. Git-commit messages
5. Walk-throughs (prep as you go). 
6. Architectural level diagrams (this is a GROUP activity not a lonely boring task)
7. Runbooks

1. Former user (Deleted) / Ruth Orhiunu (Unlicensed) / All Dev team
2. All Dev team
3. All Dev team
4. All Dev team
5. All Dev team
6. Reuben Noot (Deactivated) / All Dev team

1. New Confluence structure proposed
2. -
3. - (Paul Hoang) Knowledge transfer on the JVM heap and some techniques on how to debug out of memory exceptions. Also had a small exercise for people to debug an actual issue

• 5 - 1st ESR walk-through by Jag
• 6 - (Suneet Kamath) - documentation of Generic upload sitting on a branch waiting for someone to pick up and run with as part of the Knowlodge transfer; shared with Reuben Noot (Deactivated), Jayanta Saha, Simon Meredith (Unlicensed)
• 7- Entry point for all runbooks. Major / live related services documented.

1. New Confluence
2. r
3. r
4. r
5. r
6. r
7. /wiki/spaces/TISDEV/pages/539525127

Development (P1s - POs to review what are P1s in Jira as a matter of urgency)

1. Reasons for adverse outcomes
2. import bugs
3. NINO
4. Reval review (Curriculum Completion date column)
5. Placement comments
6. Sub-specialty
7. Mapping metadata from the document management import
8. Prioritising and responding (where necessary) Intrepid / TIS links

• (Paul Hoang) New Assessment outcome reason link
  (Paul Hoang) Assessment outcome reason ETL

• (Suneet Kamath)
  • Unplanned/Spike/Epic : Revert & Reinstating Sanitiser code
  • TISDEV-4009 : allow crashed jobs to be restarted after a set time. Has the side benefit of allowsing multiple generic upload services to be run simultaneously for HA 
  • TISDEV-4803 : exception handle backend validations on TCS api and improved error formatting
    TISDEV-4825 fix for WTE not working on templates depending on cell formatting/possibly excel versions !
    TISDEV-4859 bump up to latest TCS client to pick up fix
  • TISDEV-4825 fix for WTE not working on templates depending on cell formatting/possibly excel versions
  • bump up to latest TCS client to pick up fix

• (Jag) NI numbers are now available in TCS (DB only and not in TIS yet). 
• -
• -
• -
• -

• The remaining local offices are live with TIS ESR interface.
• Knowledge Transfer to Jayanta is in progress.
• Planned enhancements and bug/issues/improvements (BAU) have been done.
• NI Number has been now made available in TCS (DB only) and ESR-ETL is now ready to send NI information to ESR.