/
CPS Retro - 09/03/2026

CPS Retro - 09/03/2026

[ Participants ] [ Retro Points ] [ Retro Summary ] [ Call outs ] [ Actions from last retro ] [ What was good? ] [ What could be better ? ] [ Ideas (What can we improve?) ] [ Actions ]

Participants

Retro Points

Some things to think about:

  1. What did we do well, that if we don’t discuss we might forget?

  2. What did we learn?

  3. What should we do differently next time?

  4. What still puzzles us?

  5. Which tools or techniques proved to be useful? Which not?

  6. What is our biggest impediment?

  7. If we could change 1 thing, what would it be?

  8. What caused the problems that we had recently?

  9. Which things went smoothly? Which didn’t?

 

Retro Summary

Call outs

 

image-20260309-112941.png

What was good?

image-20260309-111833.png

What could be better ?

 

image-20260309-111931.png

 

Actions

Owner

Action

Due Date

Owner

Action

Due Date

@Lee Anjella Macabuhay

Documentation on CI stuff on how it works
K6 and Kubernetes should be treated like the sonarqube stuff**

Next retro

Call a workshop and advise session with Kraken team

Next retro

1 hr session on AI sharing with team

Next retro

@Toine Siebelink @Shivani Khare @Seán Beirne @Gerard Nugent @Lee Anjella Macabuhay

AI experimenting

-

@Toine Siebelink

Need to follow up on the “Process Workshop” pending

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

  • AI experimenting and share with team