action #176205
closed[retro][experiment] Avoid running overtime in our daily standups - 5m break between dailies size:S
0%
Description
Motivation¶
From #175971 . Discussed in QE Tools coffee break 2025-01-27. We decided to run the experiment to shift the dev daily back by 5m.
Acceptance Criteria¶
- AC1: Explicit decision within the team was done about 5m break between dailies after sufficient experiment run time
Suggestions¶
- Update wiki and invites
- Announce the change
- Help moderators to remind ourselves
- Review the execution of the experiment after reasonable time and make a decision with the team if we should continue, revert or do something different
Updated by okurz 3 months ago
- Copied from action #175971: [retro] Avoid running overtime in our daily standups size:S added
Updated by okurz 3 months ago
- Due date set to 2025-03-14
- Category changed from Feature requests to Organisational
- Status changed from In Progress to Feedback
- Priority changed from High to Low
- Target version changed from Ready to Tools - Next
I updated https://progress.opensuse.org/projects/qa/wiki/Tools#Team-meetings, updated the Slack workflow and sent a new time proposal for the google calendar invite (can't update the event itself). I also wrote an announcement in our team chat room in https://suse.slack.com/archives/C02AJ1E568M/p1737983197173669
@here dev dailies will now be running each work day 0940Z-0955Z, i.e. 5m later. See https://progress.opensuse.org/issues/176205 for details
Updated by okurz about 1 month ago ยท Edited
Asked in https://suse.slack.com/archives/C02AJ1E568M/p1741853385441329
- Stay with the new, current schedule infra:1020-1035+dev:1040-1055 (5)
- Revert to the old schedule infra:1020-1035+dev:1035-1050 (1)
- Try something different like infra:0930-0945+dev:1015-1030 (3)
- Need to research more how to do work in 2025 (2)
Are you ok to keep the current schedule as the majority voted for that or would you like to try to convince others?
Updated by okurz about 1 month ago
- Due date deleted (
2025-03-14) - Status changed from Feedback to Resolved
No objections so with that we should stay with 1. and resolve.