CPS Retro - 01/09/2025
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
Call outs
Actions from last retro
Owner | Action | Notes | Due Date |
|---|---|---|---|
@Lee Anjella Macabuhay | Ultimate IntelliJ team share update | what do you use? what do you find helpful? | Next Retro |
See if plots ‘updates’ is enough or need improvements? |
| Next Retro | |
Knowledge sharing update | Update calendar on the schedule | Next Retro | |
Check with David about Team building/training | Team activity update | Next Retro | |
Knowledge sharing between EST and ETH |
|
| |
@Kolawole Adebisi-Adeolokun | See more strict Requirements gathering process | suggestion ‘definition of ready’ ? | Next Retro |
@Priyank Maheshwari | see deployment strategy | See what E// does | Next Retro |
@Gerard Nugent | Ger on vulnerabilities knowledge sharing | Call knowledge sharing session on past security updates and vulnerability fixes with team | Next Retro |
@Levente Csanyi | Follow up on communications with ETH team | Call a meeting to update team on this progress | Next Retro |
Team (everyone) | Deprecating old wiki files | if a feature or study isc current and has/had old wiki pages , put the the old wiki pages with ‘Deprecated heading’ add old/new links to relevant pages | Recurring |
Camera use on team calls | Be more proactive in turning on cameras in team calls | Recurring |
What was good?
What could be better ?
Ideas (What can we improve?)
Actions
Owner | Action | Due Date |
|---|---|---|
@Lee Anjella Macabuhay | Create new Jira ticket - Wiki on a Knowledge Transfer (KT) session at one place. | Next retro |
Create schedule for members to rotate on giving some IntelliJ new tip or hack for team (Proactiveness in leveraging tools we have) | Next retro | |
Team | Always remember this stand up prompt: “Are you stuck???” | Next retro |
@Toine Siebelink | Assign new Committer | Next retro |
PLEASE NOTE THE FOLLOWING RECURRING ACTIONS FOR TEAM MEMBERS !
Self review before asking others to review
code should be self reviewed by author to avoid wasting time on small changes
Ping the Teams channels for both teams to have your code reviewed after you pushed it up, not just in stand up!
i.e. the code is pushed at 2pm and author only notifies team next day stand up for review is a NO-NO
Ping the code committer when you have comments that can be more quickly explained on call!
ONAP GERRIT commits
Commit title must have prefix to explain status, especially on WIP commits, example:
[BLOCKED] Event schema update
[POC] one schemaset per module set tag
POC commits
should stay in Nordix
should be part of a study
User stories must be groomed before starting any progress
Prioritize your own meetings
if you are CC on call , then it is optional for you to come
Share good courses for team
2-3 user stories on your board
No build up in ongoing user stories in your board
team member should only have about 2/3 user stories - any more should be looked at for delegation
Encouraged camera on in meetings
there has been a decline of this recurring action the past few months#
Check calendar every Monday stand up
Prepare before hand for when doing a grooming on Mondays