CPS Retro - 11/08/2022

Owned by Joseph Keenan
Last updated: Aug 11, 2022
2 min read

 

Aug 11, 2022 

 

Participants

@Joseph Keenan 

@Toine Siebelink 

@Former user (Deleted) 

@Dylan Byrne 

@Sourabh Sourabh 

@Lee Anjella Macabuhay 

@Andras Zoltan Kiss 

 @Aditya Puthuparambil 

 

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?

 

Subject

What went well

What didn't go well

What can be Improved

Puzzle/Blocker

Subject

What went well

What didn't go well

What can be Improved

Puzzle/Blocker

1

Reviews/tasks/docs

  1. Improved review process speed/turn-over

  2. Code review process (Code Quality)

  3. Documentation has improved

  4. Work Item owners work well

  1. Implementation proposal pages could better organised

  1. become clearer about who is assigned to a Jira using reviewers in gerrit

  2. is everyone participating equally in reviews

  3. earlier sharing of reviews

  4. Code review comments need more description

  5. Lower number patchsets would be good

  6. Replies to code review comments could be more timely

 

2

Responsibilities

  1. Sharing work

  2. Team collaboration is working together as a group on a project, process, or concept to achieve a better

 

 

 

3

Performance/Env

  1. performance bugs slow

  2. just one person working on these

  1. Performance environment

  2. We don't see performance issues as architecture issues

  1. share with others

  2. report of performance issues, progress

 

4

Staffing/Communications

  1. too many people leaving :-( Bell opted out

  2. BT starting to participate

  3. Luke will be participating with new team

  4. Miklos and Andras coming over in Spt ?

  1. attendance during Tuesday in office, maybe better after summer

  2. Aditya no longer full time on CPS :-(

  3. Team members left

  4. Losing information and historical information as people leave

  1. Inquire if communication with Wipro can be improved 

  2. Have some "Guardian" (WIO) for work item (technical/managerial)

  3. Are there courses for WIO and the team in general to develop soft skills

  4. Aditya would like to be more involved in CPS

 

5

Software/Bugs

 

  1. Bugs coming up are not that descriptive and missing files, steps, etc.

  1. Fault slip analysis (FSA) should be done for major bugs

  2. .KT OOM (Kubectl)

  1. lliquibase changes, is it the best approach?

6

Meetings/WoW

  1. Early scrum meeting(Better planning for the day)

  2. Team meeting every 2 week

  3. Team working towards common goal

  4. Pair programming working well

  5. Wiki pages for the team are owned by the team and are useful

  1. Backlog grooming (More questions need to be asked)

  1. Better grooming sessions and more of them

  2. No US points

  3. Because of refactoring scope creep can occur

  4. More detailed descriptions for tickets (and keep them up to date)

  5. Create more sub tasks if ttey are needed

  6. More wikis for the team and by the team should be created

  7. Retros can be more focused on the team

  8. Dave to add Aditya to biweekly meeting

  9. Extend coffee break (Tuesday onsite)

 

7

Learning

  1. Lots to learn

  2. Miklos good PP sessions with Andras

 

 

 

 

Actions

Action

Notes

Assignee

Action

Notes

Assignee

1

Implementation proposal pages could better organised

 

@Joseph Keenan 

2

KT OOM (Kubectl)

To contact Gareth for help

@Aditya Puthuparambil 

3

FSA

 

@Toine Siebelink 

4

Team add correct reviewers to reviews

WIO & 2 others

ALL

5

Discuss with team for performance testing 

Invite Dave Donnelly and Aditya

@Sourabh Sourabh