Skip to content

Commit ac9628b

Browse files
Added sprint retrospective notes for retro 2025-08-28
1 parent 3324660 commit ac9628b

File tree

1 file changed

+71
-0
lines changed

1 file changed

+71
-0
lines changed
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
# 2025-08-28
2+
3+
## Sprint 2025-08-28 Retrospective (2025-10-01)
4+
5+
| Chair | Timekeeper | Note Taker |
6+
|-------|------------|------------|
7+
| TW | KB | IG |
8+
9+
## Items from previous Retrospective
10+
### NDW1926 Linux build?
11+
- *ACTION*: FA To check with CMS how to adopt Windows 10 LTS for build server.
12+
13+
### ISIS Shares (\\isis\shares) organisation - have not got around to it yet.
14+
- Carry over to next retro.
15+
16+
## Items from this retrospective:
17+
### Review of First Line Support
18+
- Discussion were had around the adoption of the first line support procedure.
19+
- GR identified that there was a problem where some issues were not picked up and missed from being actioned.
20+
- GR suggested a formal handover at the end of a week, perhaps write up a Friday summary of the week.
21+
- GR mentioned that Top Desk is the corporate platform and maybe we should look at using it.
22+
- FA Mentioned Jira, but it's not free and we would need to look at licensing.
23+
- FA suggests adopting a system where we can enter issues and close them out.
24+
- *ACTION*: FA to consider options in conversation with team members.
25+
26+
### Developer Manual - protection of master branch
27+
- There was a bit of a debate in comparison between the ease of updating the manual versus the
28+
ideology that documentation should be at the same quality as code.
29+
- It was decided that instead of committing directly to master, we should have a trial period of
30+
creating PRs and flash-reviews. This policy should be reviewed at a later date to consider its efficacy.
31+
32+
### Documentation on wiki instrument-information--hotfixes
33+
- JH raised the question as to whether we need to our hotfix/deploy process and suggests that we
34+
should either keep the hotfixes page up to date or remove it.
35+
- FA suggests creating a flash review or ticket.
36+
- Remove the Hotfix column.
37+
- Deploy scripts to not prompt to add text to the hotfix column.
38+
39+
### Wiki instrument information pages are significantly out of date
40+
- GR asked whether we should make an effort to improve them, as having a page is useful for instrument support?
41+
- TW posed the question as to whether we should use the existing pages as a starting point or bin them and start again?
42+
- *ACTION*: TW to place a warning at the top of every page stating that the current information is
43+
historical content and may not be up to date.
44+
45+
### Disc space
46+
- TW stated that small discs on various machines has caused repeated issues.
47+
- *ACTION*: GR to set up a group meeting with CMS to discuss.
48+
49+
### Wierd permissions on stage-deleted
50+
- Could we modify permissions of the stage-deleted folder or perhaps don't use it?
51+
- Issue bumped until CMS is available to discuss.
52+
53+
### Timings of deploys
54+
- GR commented that deployments being scheduled only a couple of weeks before cycle and during Summer holidays
55+
can be problematic, the Summer being of particular issue.
56+
- We should attempt to deploy a week earlier and deliver demos earlier.
57+
58+
### Deploy script refinement
59+
- TW pointed out that occasionally a manual step in the deployment process does not get done, but
60+
there is no check that it actually has been done.
61+
- The Roadmap should incorporate procedures to address this.
62+
63+
### Renaming of 'server-common'
64+
- JH suggested that we should rename 'server-common' to 'ibex-ca-helpers'.
65+
- FA suggested 'ibex-epics-helpers'
66+
- *ACTION*: JH to find some suitable names
67+
68+
### Galil-old branch
69+
- FA suggested that a repo check on galil-old would be a good idea.
70+
- *ACTION*: FA to create a ticket to create a repo check on galil-old.
71+

0 commit comments

Comments
 (0)