Availability
(assume Team Availability Calendar is up to date, otherwise, everyone is available for 9 days):
Joanne Ify Ola Panos Chris | -3.5 -1 -3 -7 -4 |
---|
Sprint Priorities
The following list was the prioritisation output from Sprint Planning - largely a stabilisation Sprint:
- BAU - POs to review what are P1s in Jira as a matter of urgency. To include:
- Rotations ID being saved rather than Rotation name / Make Rotation name a read only field
- One London office can't create posts (Chris / John G and Sunil) TISDEV-4854
- Technical debt +
- 15 votes: Increase team knowledge of TIS big picture
- 14 votes: Testing so we can release with confidence
- 12 votes: Pipeline replacement
- 12 votes: E2E test coverage (ESR)
- 11 votes: Filming the team – this is who we are!
- 10 votes: Integration tests
- 9 votes: Clearly define a domain model – a clear representation of what TIS is
- Replacing jHipster front end code
- TIS NDW mappings
- Knowledge transfer
- Confluence housekeeping - especially deleting documentation that is out of date
- Coding standards (Dev meeting / series of meetings)
- Pairing / Mobbing
- Git-commit messages
- Walk-throughs (prep as you go).
- Architectural level diagrams (this is a GROUP activity not a lonely boring task)
- Development (P1s - POs to review what are P1s in Jira as a matter of urgency)
- Assessments – continuing work (Paul)
- Placement comments - P1s in Next Up (Suneet)
- Removal of deleted records (Alice confirmed)
- NDW UAT feedback analysis – Product team (support needed once HiCom turn on the TIS-Intrepid ETL to switch on their modules - Friday?)
- Discovery/research – replacements for HICOM modules (CPPS, Placement Manager, Leave Manager, CBMS) and trust and trainee portal - Product team (Rob to confirm priorities within this)
- Sub-specialty (fixed on dev - check just waiting for release - Ola)
- Mapping metadata from the document management import (Luis)
- People / Posts paramatised - TISDEV-4926 (1 day Spike) / TISDEV-4927 (long term solution to Paul's prototype) / WAF / Analysis around sanitiser
- ESR (DevOps) needs refactoring (Fred)
- DR planning - incl. geo-replication, roll back and build again scenarios (John S and Ops)
Contents
The following items to be shared by team members during this sprint review
Item | Owner | Description of work | Link. e.g. to working software https://apps.tis.nhs.uk/ (note: use Dev for obfuscated data) | Loom video of completed work https://www.useloom.com/ |
---|---|---|---|---|
Production Application releases / updates | Releases | |||
BAU (incl. Rotations ID being saved rather than Rotation name / Make Rotation name a read only field, and One London office can't create posts TISDEV-4854 (Chris / John G and Sunil)) | ||||
Technical debt +
| Paul |
| ||
Knowledge transfer
|
| Paul
Jag
| Jag: https://github.com/Health-Education-England/TIS-ESR-ETL Ashley: ESR-ETL Timings: | |
Development (P1s - POs to review what are P1s in Jira as a matter of urgency)
|
| Paul
9. Jag/Fred
Jag: Looked in to some issues raised by ESR.
| https://www.useloom.com/share/30b62ba412464620a69c1623d70f72fd 9. Jag/Fred https://build.tis.nhs.uk/jenkins/job/tis-esr-ftpsync-cron-stage/ https://build.tis.nhs.uk/jenkins/job/tis-esr-ftpsync-manual/ | |
Resource Planning | Agency update Advert gone out for two BA roles (London-based) to give us a head-start on recruiting TIS Team #2, which will be an outside of London-based team. Full Time recruitmentNo joy with the final FED role as yet. OtherRuth left us |
Add Comment