CPS Retro - 19/05/2025
Participants
@Lee Anjella Macabuhay
@Sourabh Sourabh
@Priyank Maheshwari
@Kolawole Adebisi-Adeolokun
@Gerard Nugent
@Seán Beirne
@Levente Csanyi
@Toine Siebelink
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 |
|---|---|---|
@Lee Anjella Macabuhay | change DND time on some Wednesdays to afternoon |
|
Get topics and set roster on knowledge sharings |
| |
Organize Knowledge sharing between EST-ETH to gather some info/resources | from previous retro Team would like to have some useful information on how CPS-NCMP is used E, or what the big picture is like inside E, for example, the use of realistic examples would be way useful if the team knows what information we are looking at or for how Priyank can relate to some 3GPP terms etc. Csaba** | |
@Toine Siebelink | Handle/plan ‘no ONAP releases’ | no more ONAP releases |
@Toine Siebelink @Levente Csanyi @david.donnelly | Need to improve communications with ETH team with Levente as ‘bridge’ | Levente to be proactive as 'bridge' - need to discuss this and see ideas maybe case by case for different teams |
@Priyank Maheshwari @Sourabh Sourabh | 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
| from previous retros
|
What was good?
What could be better ?
Ideas (What can we improve?)
Actions
Owner | Action | Notes | Due date |
|---|---|---|---|
@Kolawole Adebisi-Adeolokun | Grooming reminders on Fridays | Monday grooming usually either run overtime or agenda is fixed only on the day. It will be better that by end of the week, we know which user stories will be groomed for the coming Monday |
|
talk to teams in E// | CPS project promotion |
| |
Team
| Prepare before hand for when doing a grooming on Mondays | If member intends to do a grooming on Monday, ensure that the ticket is pre filled as much possible to allow estimating time needed for the grooming session |
|
Check calendar every Monday stand up | To allow the team to be aware of any absence for the week, on stand ups every Monday, the team calendar should be checked to confirm absences for the week |
| |
@Lee Anjella Macabuhay | Assign second ‘lead’ for an epic | Go through the current epics and ensure there is a ‘second’ lead for each epic that is aware of the said epic’s progress | Next retro |
Check for summer team event/summer bbq | Check with line manager for possibility of team event for summer |
| |
Organize Knowledge sharing between EST-ETH to gather some info/resources | from previous retro Team would like to have some useful information on how CPS-NCMP is used E, or what the big picture is like inside E, for example, the use of realistic examples would be way useful if the team knows what information we are looking at or for how Priyank can relate to some 3GPP terms etc. Csaba** |
| |
@Seán Beirne | Developer guide on licensing | Create a guideline for future developers on team following the 3GPP epic obstacles regarding licensing of ProvMns | Next retro |
@Levente Csanyi | Need to improve communications with ETH team with Levente as ‘bridge’ | from previous retro Levente to be proactive as 'bridge' - need to discuss this and see ideas maybe case by case for different teams |
|
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