...
Actions from last retro
See Actions: CPS Retro - 04/06/2024
| Owner | Action | Notes | Team Rating |
|---|---|---|---|
(Escalation) To communicate with E to define roles/responsibilities in terms of epics/stories/prioritization decision making . | For next retro , hopefully to be resol;ved by meeting for next retro | ||
Cross team meeting on new way of implementing user story breakdown | To be done for next retro > Didn't have time | - | |
Clarify names on the tests (i.e. Integration tests) and create guidance for team | To be done for next retro Levente Csanyi - renaming folders right now still need to follow up on use of Acceptance tests | - | |
On user stories -
| > (E) has been better on writing acceptance criteria ; Steps to reproduce still needs to be provided though! |  | |
On bugs - say 'NO' more often especially when there is not enough information! | **see note on point above | | |
On release notes - Update release notes with commits if possible
| |
...
| Owner | Action | Notes | Due Date |
|---|---|---|---|
Call 'retrospect' like meeting with (E) to discuss ways of working with CPS team. | CPS team has repetitive points from previous retrospective meetings that relates to the E team Example of points to discuss
Lack of communication and involvement needs to be resolved here. | Next retro
| |
Follow up to ask Peter K or (E) regarding new team integration (for datajob) | |||
| Toine Siebelink | Update the wiki page for information about tests | There is an existing page regarding tests but has not been updated for a while. | Next retro
|
| Cross team meeting on new way of implementing user story breakdown | From previous retro | Next retro
| |
| Clarify names on the tests (i.e. Integration tests) and create guidance for team | From previous retro | Next retro
|
...