Skip to content

Instantly share code, notes, and snippets.

@joseivanlopez

joseivanlopez/review-improvements.md

Last active October 24, 2024 08:12
Show Gist options
  • Save joseivanlopez/ba022be466ed5455c46486c891d69b09 to your computer and use it in GitHub Desktop.
Save joseivanlopez/ba022be466ed5455c46486c891d69b09 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
review-improvements.md

Feedback from QE

  • +5 List of PR & blog that can change our test cases or more related with the UI, CLI.

  • +3 Don't understand, hard to follow.

  • +3 Keep the demo but with changes.

  • +2 For bug resolution in Agama they would like to see where it is fixed and how. Also there are some with interest in rust that would like to see sometimes internal. But this would be on demand.

  • +2 Interested on agama architecture, how some components communicate with others, that would help to understand developer's task.

  • +1 Get list by email to study the topics with some day(s) on advance.

  • +1 Demo not practical enough, for instance, pre/post feature was presented with an 'echo' instead of using a more real user scenario (looked theoretical).

  • +1 PO and SM is enough to join the meeting.

  • +1 Some topics are really internal of Agama and we can skip this part or they should be better timeboxed.

  • +1 Feel insecure asking about your technical desicion or what to request or not during the meeting, they feel that they cannot change what they did.

  • +1 Have meeting minutes.

Possible Improvements

  • Dev post after each sprint:

    • +5 List of PR & blog that can change our test cases or more related with the UI, CLI.
    • +1 Have meeting minutes.

  • Agama open-door sessions:

    • +3 Don't understand, hard to follow.
    • +2 Interested on agama architecture, how some components communicate with others, that would help to understand developer's task.
    • +1 Some topics are really internal of Agama and we can skip this part or they should be better timeboxed.
    • +1 Feel insecure asking about your technical desicion or what to request or not during the meeting, they feel that they cannot change what they did.

  • Advance a summary of QE interesting topics (e.g., on Friday before review):

    • +5 List of PR & blog that can change our test cases or more related with the UI, CLI.
    • +3 Don't understand, hard to follow.
    • +1 Get list by email to study the topics with some day(s) on advance.

  • More and better demos:

    • +2 For bug resolution in Agama they would like to see where it is fixed and how. Also there are some with interest in rust that would like to see sometimes internal. But this would be on demand.
    • +3 Keep the demo but with changes.
    • +1 Demo not practical enough, for instance, pre/post feature was presented with an 'echo' instead of using a more real user scenario (looked theoretical).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment