CPS Retro - 09/02/2025
- Lee Anjella Macabuhay
Participants
@Lee Anjella Macabuhay
@Sourabh Sourabh
@Priyank Maheshwari
@Kolawole Adebisi-Adeolokun
@Levente Csanyi
@Gerard Nugent
@Seán Beirne
@Halil Cakal
@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 - 12/11/2024
Owner | Action | Notes |
|---|---|---|
@Kolawole Adebisi-Adeolokun | Update/new FS requirement and CPS performance and robustness requirement (stakeholder) | ongoing sign off on requirement still needed |
@Lee Anjella Macabuhay | Schedule meeting to discuss w.o.w for CPS
|
|
"CPS DND" for the team ~2 hrs (Wednesday) | DND helped team | |
@Lee Anjella Macabuhay @Daniel Hanrahan | Look at how to handle bugs/tech debt (priority , open) |
|
@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 | knowledge share for February
|
@Priyank Maheshwari | Analysis for CPS to use Kubernetes deployment for our testware and troubleshooting (see backlog for ticket)
|
|
@Halil Cakal | Define on demand performance job (#commit) |
|
@Seán Beirne | Improvement on postman collection in CPS Repo |
|
@Toine Siebelink | Delegate ONAP items/tickets |
|
CPS TEAM , Sub teams | Self review before asking others to review |
|
What was good?
What could be better ?
Ideas (What can we improve?)
Actions
Owner | Action | Notes | Due date |
|---|---|---|---|
@Kolawole Adebisi-Adeolokun | Update/new FS requirement and CPS performance and robustness requirement (stakeholder) | ongoing | ongoing sign off on requirement still needed |
@Lee Anjella Macabuhay @Daniel Hanrahan | Look at how to handle bugs/tech debt (priority , open) | from previous retro |
|
@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
| By the end for February, i.e. one of the following knowledge sharing sessions
|
@Priyank Maheshwari | Analysis for CPS to use Kubernetes deployment for our testware and troubleshooting (see backlog for ticket)
| from previous retro
| next retro |
@Halil Cakal | Define on demand performance job (#commit) | from previous retro | next retro |
@Seán Beirne | Improvement on postman collection in CPS Repo | from previous retro | next retro |
@Lee Anjella Macabuhay | Set up EST-ETH retro |
| next retro |
Organize Knowledge sharing between EST-ETH to gather some info/resources | 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. | next retro | |
@Kolawole Adebisi-Adeolokun | Clean Tech debt/ Backlog | a lot of old or duplicated user stories that needs to be tidied up with some team members | next retro |
@david.donnelly @Toine Siebelink @Levente Csanyi @Gerard Nugent | Need to improve communications with ETH team with Levente as ‘bridge’ | Levente to be proactive as 'bridge' - need to discuss this and see ideas | next retro |
@Toine Siebelink | Sort R16 page | Suggestion of changing coloring of requirements (i.e. in progress, blocked,…) | next retro |
Share progress of DCM open sourcing talks with @Gerard Nugent |
| next retro | |
@Gerard Nugent | Propose strategic approach on 200K work epic | Suggestion of categorizing the work that is in/comes under the 200K epic | 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
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
Call outs