Page Comparison

Production Application releases / updates

Releases

TIS-51

BAU - POs to review what are P1s in Jira as a matter of urgency. To include:

1. PO Group to clarify the top P1s - Alistair Pringle (Unlicensed), Joanne Watson (Unlicensed), Former user (Deleted), Ashley Ransoo, could you please set aside sometime in the next few days to do this? Use Andy to help with communicating priorities to the Dev team.
2. Jayanta and Hamed, supported by John will form a BAU team this Sprint to focus on Bugs.
   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

Jayanta Saha

Former user (Deleted)

John Simmons (Deactivated)

Technical debt +

1. 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 fee in.
2. Field validation - BA piece to help incremental safe approach / liaise with Devs to make sure the 30 odd tickets reflect the work necessary.
3. Extending dropdowns - some areas where we have reference data not properly held in the app (hard coded, rather than in a table, etc).

All team

TIS Testing:

1. Implement Testing strategy and Planning for the Different type of testing in TIS
https://hee-tis.atlassian.net/wiki/spaces/TISDEV/pages/591757371/TIS+Testing+Strategy+Future+Approach
2. Created a Defect Management Process Strategy. Setup the defect Triage meeting with PO/BA's on weekly basis to help in Defect Triage Process.
https://hee-3. tis.atlassian.net/wiki/spaces/TISDEV/pages/615251969/TIS+Defect+Management+Process
3. Gherkin Template with DOD and DOR has been created to create the story in BDD manner.
https://hee-tis.atlassian.net/wiki/spaces/TISDEV/pages/598016124/Gherkin+template+for+User+Story
2. Created Test Resource Plan for the different type of testing areas
https://hee-tis.atlassian.net/wiki/spaces/TISDEV/pages/601751644/Test+Resouce+Allocation
5. ESR-ETL Testing design, Strategy and Planning with Jag and Ashley. ESR interfaces testing strategy sketch for Contract Testing and Integration Testing has been finalised.
Link: https://hee-tis.atlassian.net/wiki/spaces/TISDEV/pages/617676877/ESR+Testing+Strategy
6. Contract Testing POC for ESR-ETL to ESR Service has already been started by Jag.
7. Test Automation release pipeline is in Progress. Co-ordinating with DevOps for Test Pipeline.
8. Catchup with Simon for BE Unit Testing. Will continue when Simon is back.
9. Support release testing, Report Bugs and Re-Testing of bugs.
10. Bulk upload session with Ashley for people.
11. Catch with Ray and Chris regarding anonymize the production data and loading the data to stage to make sure both environments have the same data and configuration and discussion about write access to the Production database.

Paul & Simon

• Added prometheus metrics endpoints to most services to push environment data
• Added health endpoints to most services to allow us to alert if a service goes down

Chris

• Configured the monitoring solution to use the prometheus metrics

Field validation is documented and available to discuss on various confluence pages, but requires extended sessions to get this done, also there are several dependencies - re-prioritised below deletion of records and adding missing data

Monitoring Demo - Memory usage stats

Knowledge transfer

1. Confluence housekeeping - especially deleting documentation that is out of date
2. Coding standards (Dev meeting / series of meetings)
3. Pairing / Mobbing
4. Git-commit messages
5. Walk-throughs (prep as you go). 
6. Architectural level diagrams (Reuben leading)

Confluence housekeeping started with Andy creating an outline for the new page structure, which was initially reviewed with the Product Owner group - it will need to continue into the next sprint

Paul

• Paired with Simon on the prometheus work and shared knowledge
• Paired with Jayanta on the audit logging to share knowledge
• Had an initial meeting on development standards to bring into the next sprint

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

1. Assessments – continuing work (Paul)
2. Document management - accessing existing documents (better dataset to work from, but HiCom not delivering till late next week, and work needed to be done on reviewing metadata before dev work should commence), and creating, updates and deletes of new ones (easier to achieve)
3. Assessments Bulk Upload - Jayanta and Hamed (with support from others where necessary)
4. Placement comments - P1s in Next Up (Suneet). Nearly done... merged awaiting TESTING and deployment
5. Removal of deleted records (Alice confirmed)
6. NDW UAT feedback analysis – Product team (support needed once HiCom turn on the TIS-Intrepid ETL to switch on their modules - Friday?)
   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.
7. Discovery/research – replacements for HICOM modules (CPPS, Placement Manager, Leave Manager, CBMS) and trust and trainee portal - Product team (meetings from Friday for PO Group to start doing this)
8. ESR (DevOps) needs refactoring (Fred)
9. DR planning - incl. geo-replication, roll back and build again scenarios (John S and Ops)
10. Adding search to enable easier adding of new sites, and changing new sites to 'current'. General refactoring.

8- https://build.tis.nhs.uk/jenkins/job/tis-esr-ftpsync-cron-stage/

Ola, Panos, Paul, Fred

• Assessments released to enable the ability to assign multiple reasons to an assessment outcome.
• Data migration of the assessment outcome reasons from the old format to the new

Jayanta

• Work in progress on placement Bulk uploads using Placement Id as matching criteria. 
• Audit logging of the TCS service.

Removal of deleted records - these have been ticketed up as a final set of data, the final set of tickets were created mid-sprint so not implemented.

NDW UAT Feedback Analysis - missing fields from TIS have been identified that would support the Data Lead view of must have's to support NDW/reporting, tickets have been created but require further refinement - to understand the answers to questions such as are the identified fields absolutely necessary, are there any other changes that can be made to reports that would render any identified field "not required", can the data be sourced from another table within TIS?

Assessments Loom Video