| Table of Contents | ||
|---|---|---|
|
Participants
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 - 06/08/2024
Owner | Action | Notes |
|---|---|---|
Clarify names on the tests (i.e. Integration tests) and create guidance for team | ||
Explore licensed version of IntelliJ for team productivity--- Report use and benefits to see if it is worth for the team to forward to Manager | Need to gather their opinions for next retro | |
Close SON use case | ||
Call a meeting on to discuss replacement of CSIT with k6 | ||
Update the wiki page for information about tests There is an existing page regarding tests but has not been updated for a while. | ||
Turn camera on for meetings | Been valuable and followed since last retro | |
Contact bug reporter informally as soon as we take on the bug | Been valuable and followed since last retro especially for big bugs |
What was good?
What could be better ?
Ideas (What can we improve?)
Actions
Owner | Action | Due Date |
|---|---|---|
Update/new FS requirement and CPS performance and robustness requirement (stakeholder) | Next retro | |
Performance requirement discussion (internally) | Next retro | |
Move sync meeting with Bora/Cerberus on Tuesday to accomodate team meetings on Mondays and Tuesdays | ASAP | |
Raise ticket on non-editable links for team as result of wiki migration | ASAP | |
Create knowledge sharing page for team and provide info how this meetings will work | Next retro | |
Schedule Grooming meetings to be on Mondays/Tuesdays | ||
Schedule meeting to discuss w.o.w for CPS
| ||
Follow up on the retirement of CPS-TBDMT as no longer used and we have maintenance cost. | Next retro | |
Provide insights on recent exploration of the licensed version of IntelliJ for team productivity--- report use and benefits to see if it is worth for the team to forward to Manager | Next retro | |
Move retro meetings on Mondays | Next retro | |
Team | Agree on meetings scheduling for Monday and Tuesday (office days) Will be changed as team gets used to the new office days set up
| Ad hoc |
Call outs
