# PIXL-FlowEHR Retrospectives

----

## Retrospective 1
27/09/2022

### Start doing
- Simplify
- Clarify responsibilities
- Greater issue granularity
- Clarify target architecture including networking
- look ahead as part of stand-ups & assignments to issues
- ? go through the board on standup to make sure have granular issues
- 1:1 catch ups on ad-hoc basis to provide further detail on tasks
- Clarify sprint goals & priorities
- Do Sprint Demos
- Aim for each PR to have a linked issue
- Highlight assumptions in issues
- Focus on high priorty with simplified options so no complex design

### Stop doing
- Reviewer branch merging (owner instead?)
- So much context switching (maybe unavoidable) +1
- less decisions on devs

### Keep doing
- Using the GH project board
- Stand-ups
- Good comms with Tom on Slack
- Single reviewer approval for PR merge
- Great to see people in person
- Very good team collaboration

----

## PIXL-FlowEHR Retrospective 2
03/10/2022

### Start doing
- All activity on the board
- Remember to use labels on issues
- Plan for sprint demo otherwise it won't happen
- Priority sorting of issues
- Volunteer on Slack to pick from backlog, ask for yes/no
- More granularity in issue definitions

### Stop doing
- avoiding splitting issues into subtasks when they become apparent

### Keep doing
- 1:1 check points with team (Rich) +1
- Updating tasks with comments
- Monitor costs

----

## PIXL-FlowEHR Retrospective 3
10/10/2022

### Start doing
- branch naming
Could we use [gh-username]/[issue-type]-[issue-number]-[issue-tag]
e.g. nels/bug-17-stuff
types {doc, ci, feature, bug}
- create issues against the correct repo
Currently some in FlowEHR that should be in Book-of-FlowEHR
Easy to do when converting draft to issue
- Style guide (create an ADN)
Some docstring comments are in reStructuredText, others in Numpy format
Doesn't matter, as long as there is consistency. Decided on RST
- showcasing options/details from investigative work items
perhaps using Weds when on site to do knowledge share/sounding thoughts
- ringfence design & thinking time
Anika & Nel
- Do backlog refinement before sprint planning

### Stop doing
- Being vague in the tickets

### Keep doing
- on-site meetings +2
Wednesday weekly meetings decided
- slack comms

----

## PIXL-FlowEHR Retrospective 4
17/10/2022

### Previous Sprint Goals
- Dave
- Deploy to UCLHAZ
- KeyVault doc
- Tom
- Final TRE deploy
- Sample Feathr features
- Anika
- Delta Lake RBAC
- `PIXL` queue with throttle
- Ben
- Complete anonymisation stub
- Start the documentation tasks for the DICOM nodes
- Harry
- Not set
- Rich
- Network options doc complete
- Speak to Harry
- Nel
- Contract signed

**Did we hit any of them?**

### Start doing
- Realistic issues
- Realistic sprint goals
- Dual monitors for team days
- Drive standups using the sprint board so can track progress.
- naming conventions review
- Create issues for blockers

### Stop doing
- PRs not linked to issues
- Issues take way more than a week
Several “Ready” issues from last sprint still in the Ready column

### Keep doing
- Wednesdays in person
- Brainstorming in person when sensible to do so
- Don't be shy to ask for help!

----
## PIXL-FlowEHR Retrospective 5
24/10/2022

### Previous Sprint Goals
- Dave
- Deploy to UCLHAZ
- KeyVault doc
- Tom
- Final TRE deploy
- Harry/Tom/Marcus
- Feathr & Purview
- deployed on sandbox
- deployable by terraform
- Feathr access from Petal
- Delta Lake
- RBAC
- DICOM node
- docs
- Contract signed
- Networking decision/SBAR

### Start doing
- LICENSE & copyright headers in the source files
- Multiple PR reviewers
- Create checklists for
- Retrospective
- Sprint Planning
meetings

### Stop doing

### Keep doing
- Engage with MS as much as possible
- Slack
- Face 2 Face

----
## PIXL-FlowEHR Retrospective 6
31/10/2022

### Previous Sprint Goals
Tom
- Add DICOM endpoints for TRE VNET
- Review PIXL/CLI Driver requirements with Anika

Dave
- Test deployment of latest TRE version to UCLHAZ subscription
- Add SOP discussion points
- Document naming convention points
- Azure Monitor set up for TRE and on-prem metrics

Anika
- Patient Executor/Task Queue

Harry
- Purview/Feathr accessibility within TRE

Ben
- DICOM de-anonymisation
- Dummy PACS\VNA setup discussion with Junaid

Rich
- Share networking SBAR on Teams
- Set up PACs/VNA discussion with Junaid/Ben
- Set up SOP discussion placeholder meeting for a week Weds with the team
- Enable discussion on PIXL requirements with Anika/Tom
- Review if any MS help required for Purview and DICOM

**Demos** - onsite demo on Weds if in a position to do so:
- Feathr - feature store (Harry)
- Message queue (Anika)
- DICOM de-identification (Ben)

### Start doing
- Create checklists for
- Retrospective
- Sprint Planning
meetings
- Ignore non-essentials!

### Stop doing
- Other stuff! :-D

### Keep doing
- Working together as a team
- Help each other

----

## PIXL-FlowEHR Retrospective 7
07/11/2022

### Previous Sprint Goals

#### Poppy (Harry)
- Terraform deployable Feathr
#### Iris (Harry)
- Purview RBAC & Feathr integration
- Terraform deployable Purview

#### Stem (Dave)
- SoP agenda
- Azure Monitor instance able to connect to FlowEHR, AzureTRE and on-prem services
- Naming conventions Markdown doc

#### PIXL
- Finalise Orthanc deployment (Ben)
- CLI driver (Tom)
- Queue (Anika)

#### Networking (Rich)
- SBAR for VPN
- Network issue
- NSGs
- FlowEHR firewall

### Start doing
- track key lessons learned, gotch-yas
- more discussion on GH
- add GH checks on PR merges
- clearer timeboxing around our spikes

### Stop doing
- other parts of your jobs! ;-P
- rolling straight from one meeting to the next on Monday PM +1

### Keep doing
- ask each other for help

------------------

## PIXL-FlowEHR Retrospective 8
14/11/2022

### Previous Sprint Goals

### Start doing

### Stop doing

### Keep doing