You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Participants


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?


Retro Summary

Actions from last retro

See Actions: CPS Retro - 04/06/2024


OwnerActionNotesDue Date

(Escalation) To communicate with E to define roles/responsibilities in terms of epics/stories/prioritization decision making .


Action from last retroNext retro

Cross team meeting on new way of implementing user story breakdown

Action from last retroNext retro

Clarify names on the tests (i.e. Integration tests) and create guidance for team


Next retro

On user stories - 

  • (E) be clear on acceptance criterias before starting especially when working with bugs
  • use right level of Jira creation i.e. 'user stories' 'sub tasks'
  • description on Gerrit for code reviews

Recurring

On bugs -

say 'NO' more often especially when there is not enough information!


Recurring

On release notes -

Update release notes with commits if possible

  • Note to add it on acceptance criteria (if it makes sense)

Recurring

Next Retro Date:

 





  • No labels