Participants
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 |
|---|---|---|
Update/new FS requirement and CPS performance and robustness requirement (stakeholder) | ||
Schedule meeting to discuss w.o.w for CPS
| ||
"CPS DND" for the team ~2 hrs (Wednesday) | ||
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 | ||
Kubernetes deployment (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 |
|---|---|---|