CPS Retro - 28/07/2025

Participants

Some things to think about:

Owner	Action	Notes	Due date

Owner	Action	Notes	Due date
@Kolawole Adebisi-Adeolokun	talk to teams in E//	CPS project promotion	Next Retro
@Lee Anjella Macabuhay	Check for summer team event/summer bbq	Check with line manager for possibility of team event for summer	Check Team training/building
	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**	Next retro
@Seán Beirne	Developer guide on licensing	Create a guideline for future developers on team following the 3GPP epic obstacles regarding licensing of ProvMns https://lf-onap.atlassian.net/wiki/x/EwDXDQ	Doc Done, KT on blacklisting/whitelisting and take away from 3gpp issues
@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	In-Progress Meeting to follow up team on this progress*

Owner	Action	Notes	Due Date

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
Team (everyone)	Camera use on team calls	Be more proactive in turning on cameras in team calls	Recurring

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