| Table of Contents | ||
|---|---|---|
|
...
Owner | Action | Notes |
|---|---|---|
Update/new FS requirement and CPS performance and robustness requirement (stakeholder) | ongoing sign off on requirement still needed | |
Schedule meeting to discuss w.o.w for CPS
| ||
"CPS DND" for the team ~2 hrs (Wednesday) | DND helped team | |
Look at how to handle bugs/tech debt (priority , open) | ||
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
| |
Analysis for CPS to use Kubernetes deployment for our testware and troubleshooting (see backlog for ticket)
| ||
Define on demand performance job (#commit) | ||
Improvement on postman collection in CPS Repo | ||
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 | Due Date |
|---|
...
Notes | Due date | ||
|---|---|---|---|
Update/new FS requirement and CPS performance and robustness requirement (stakeholder) | ongoing | ongoing sign off on requirement still needed | |
Look at how to handle bugs/tech debt (priority , open) | from previous retro | ||
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
| |
Analysis for CPS to use Kubernetes deployment for our testware and troubleshooting (see backlog for ticket)
| from previous retro | next retro | |
Define on demand performance job (#commit) | from previous retro | next retro | |
Improvement on postman collection in CPS Repo | from previous retro | next retro | |
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 | |
Clean Tech debt/ Backlog | a lot of old or duplicated user stories that needs to be tidied up with some team members | next retro | |
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 | |
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 | ||
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
...