This repository has been archived by the owner on Apr 24, 2024. It is now read-only.
Add Meeting Notes from Scrum Meeting 04.04.2024 #1245
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
markus2330
approved these changes
Apr 6, 2024
|
|
||
| The main questions to answer: | ||
|
|
||
| - How can we improve the way we do issues? |
There was a problem hiding this comment.
Suggested change
| - How can we improve the way we do issues? | |
| - How can we improve the way we create and work on issues? |
| The main questions to answer: | ||
|
|
||
| - How can we improve the way we do issues? | ||
| - How can we improve the way we deal with Reviews of PR |
There was a problem hiding this comment.
Suggested change
| - How can we improve the way we deal with Reviews of PR | |
| - How can we improve the way we deal with reviews of PRs? |
| Takeaways: | ||
|
|
||
| - Every 3 weeks, include a 30min retro in the meeting by Andrei | ||
| - After releases, have small Demo so team is up to date with what's new. |
There was a problem hiding this comment.
Suggested change
| - After releases, have small Demo so team is up to date with what's new. | |
| - After releases, we have small demo so team is up to date with what's new. |
| - Every 3 weeks, include a 30min retro in the meeting by Andrei | ||
| - After releases, have small Demo so team is up to date with what's new. | ||
| - Explore how GitLab can help us structure issues around Use Cases/Features | ||
| - Try to have only isses that have an estimation of one week (can be done in the scope of one "sprint") - If they are too big, they should be broken down into sub-tasks |
There was a problem hiding this comment.
Suggested change
| - Try to have only isses that have an estimation of one week (can be done in the scope of one "sprint") - If they are too big, they should be broken down into sub-tasks | |
| - Try to have only issues that have an estimation of one week (can be done in the scope of one "sprint") - If they are too big, they should be broken down into sub-tasks |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Basics
close #X, are in the commit messages and changelogChecklist
First Time Checklist
Review