-
- [x] Set up recurring invites for daily scrum and bi-weekly sprint retrospectives/review/planning sessions
- [x] Invite Rene to ZenHub board
- [x] Invite Rene to Teams channels
- [x] Provide Rene wi…
-
After the new Documentation section is created (#533), add a new "Work items" document under "What documentation should exist" (in documentation/guidance folder).
Ideas for content:
- Epics/Feat…
-
- group must be voted on to create
- create repo omigroup/yournewgroup
- create basic readme with: What this group is, when you meet, how to get involved.
- create backlog in your repo for tracki…
-
Based on the [1.4 release retrospective discussion](https://docs.google.com/document/d/119PCr2h3Wwm7XA_qHqtda017Q--yWPF9u7nuUWo0ZnY/edit#), the 1.4 release team would like to propose that all release-…
-
The idea is to move the retrospectives from the end of the cycle to the second half of it. This provides faster feedback loops to catch-up on issues and follow-ups. It also enables the team to solve p…
-
Look through existing material, see what we have to change to make this a teamwork course instead of agile course. Create new issues, or for small changes create a new PR.
-
For a new team without any retrospective board, retrospective page is coming as blank. The extension can currently only
used by teams which have already retrospective boards.
-
How might we surface team wins from retro data when there may be natural behaviors from the team in the retrospective of acknowledging success, hitting goals, etc.?
### AC
- Design uncertainty 3
…
-
This will be a Slack call after the release, with at least a week of notice in the #Release Slack channel.
A bulleted list of all proposed agenda items in this issue (whether at the top or in a com…
-
We had migrated collection from Onprem to ADO Cloud.
post migration installed Retrospectives in cloud but data is missing.
Could you please help me to fix it.