Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  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

(smile)

What didn't go well

(sad)

What can be Improved

(thumbs up)

Puzzle/Blocker
1Reviews/tasks/docs
  1. Improved review process speed/turn-over
  2. Code review process (Code Quality)
  3. Documentation has improved

  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

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



3Performance/Env
  1. performance bugs slow
  2. just one person working on these
  1. Performance environment
  1. share with others
  2. report of perfoamcne issues, progress

4Staffing
  1. - too many people leaving :-( Bell opted out
  2. Adity no loger full tim on CPS :-(
  3. BT starting to particpate
  4. Luke will be participating with new team
  1. attendeance during Tuesday in office, maybe betetr after summer
  2. Team members left


5Software/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?
6Meetings/WoW
  1. . Early scrum meeting(Better planning for the day)
  2. Team meeting every 2 week
  1. Backlog grooming (More questions need to be asked)



Actions

#ActionNotesAssignee
1


...