Participants
- Toine Siebelink
- Lee Anjella Macabuhay
- Halil Cakal
- Gerard Nugent
- Sourabh Sourabh
- Seán Beirne
- Priyank Maheshwari
- Daniel Hanrahan
Retro Points
Some things to think about:
- What did we do well, that if we don’t discuss we might forget?
- What did we learn?
- What should we do differently next time?
- What still puzzles us?
- Which tools or techniques proved to be useful? Which not?
- What is our biggest impediment?
- If we could change 1 thing, what would it be?
- What caused the problems that we had recently?
- Which things went smoothly? Which didn’t?
Retro Summary
Actions from last retro
See Actions: CPS Retro - 04/06/2024
| Owner | Action | Notes | Team Rating |
|---|---|---|---|
(Escalation) To communicate with E to define roles/responsibilities in terms of epics/stories/prioritization decision making . | For next retro , hopefully to be resol;ved by meeting for next retro | ||
Cross team meeting on new way of implementing user story breakdown | To be done for next retro > Didn't have time | - | |
Clarify names on the tests (i.e. Integration tests) and create guidance for team | To be done for next retro Levente Csanyi - renaming folders right now still need to follow up on use of Acceptance tests | - | |
On user stories -
| > (E) has been better on writing acceptance criteria ; Steps to reproduce still needs to be provided though! |  | |
On bugs - say 'NO' more often especially when there is not enough information! | **see note on point above | | |
On release notes - Update release notes with commits if possible
| |
What went well ?
What didn't go well ?
Actions
| Owner | Action | Notes | Due Date |
|---|---|---|---|
Call 'retrospect' like meeting with (E) to discuss ways of working with CPS team. | CPS team has repetitive points from previous retrospective meetings that relates to the E team Example of points to discuss
| Next retro
| |
Follow up to ask Peter K or (E) regarding new team integration (for datajob) | |||
| Toine Siebelink | Update the wiki page for information about tests | There is an existing page regarding tests but has not been updated for a while. | Next retro
|
| Cross team meeting on new way of implementing user story breakdown | From previous retro | Next retro
| |
| Clarify names on the tests (i.e. Integration tests) and create guidance for team | From previous retro | Next retro
|
Call outs
Discussion Notes:
- Retros will now stay to be every 4 weeks but will now be for only 1 hour
- Discussions shall be only about 'things we can control in the team'
- Team reshuffling will be epic-based
- Code structure will now be 'feature based'
- This should be noted on grooming of user stories
- Code reviewers should also review where code is placed
- On accepting bugs, there shall be no exceptions on any items that needs to be provided before work is started on it (i.e. steps to reproduced should not be missed)
- Keep everyone in team on loop on grooming, proposals and reviews regardless if they're working on the story or not (example. cm notification subscription missed to discuss points with other team that are not working on the epic story which led to not having a 'third eye' on the design)
Next Retro Date: