-
Notifications
You must be signed in to change notification settings - Fork 2
Retrospective notes 2023.02.01
David Keymer edited this page Feb 20, 2023
·
8 revisions
Chair | Timekeeper | Note Taker |
---|---|---|
?? | ?? | David Keymer |
Items from last retrospective:
Is point allocation for support appropriate?
- Best to apply points earlier in the sprint
Migrating to new GitHub projects system and separating issues
- Decided not to use GitHub Pages for the moment, but will review at later date
Coffee
- Too tricky to invite MANTID group to coffee (as they work remotely more often), but should be possible with accelerator controls group. FAA talking to Ivan about this anyway
- Discuss when ticket is next proposed (at following planning meeting)
- Try to be better about adding tickets that anyone can work on
- OK to add urgent tickets any time
- Group would rather not have more context switching with more frequent and shorter meetings
- Suggested splitting tickets down further, but some can't be and so still wouldn't be finished by sprint end
- Decided to keep as is, but bear in mind the option in future
- Agreed that indication useful for air quality if nothing else
- Dilemma between high CO2 levels and temperature with windows open
- SHE group and/or Estates to be contacted for current policy -> TL to do this.
- Good to have Hannah & Sonya there for alternative perspectives
- Suggestion to discuss long-term plans more often -> TL to elaborate
- Hopefully ideas from the day will be implemented, or at least prioritised with rest of work
- Feeling that the group could get on with the migrations. KB agreed, but reported team too stretched to cope at moment
- Remaining migrations have most equipment catered for, tickets will be proposed as training for new starters. Starting soon with PEARL and HIFI.
- TS1 & TS2 coming up soon, so best not to take too much on at moment
Prediction that TS1 coming back will generate many problems for group, having not been run for ~18 months
- Lots of equipment has been switched off and/or disconnected during that time, so group is expecting calls even if the problem is not actually with the control software itself (but shows symptoms of course)