action #175971
closed
[retro] Avoid running overtime in our daily standups size:S
Added by livdywan 9 days ago.
Updated 4 days ago.
Category:
Feature requests
Description
Motivation¶
After conducting both infra and dev daily we found we didn't manage to stay within the time on either and still missed important points. This is not always the case but we collected feedback and found that there might be room for improvement so we can avoid this happening so often.
Acceptance Criteria¶
- AC1: At least one experiment has been chosen
Suggestions¶
- Grab the ticket and lead the conversation
- Start a conversation in chat or in a voice call
- Pick one or more ideas that several people like, propose the change(s) to our process and update the wiki accordingly
- Remember we decide as a team so don't just change something without asking
Related issues
1 (1 open — 0 closed)
- Status changed from In Progress to Feedback
We have the following suggestions so far:
- Double the time of the daily
- Have a 5 minute break between infra and dev daily
- Merge topics and have one daily, 15 minutes total with time for follow-ups after
See also the conversation in Slack
livdywan wrote in #note-1:
We have the following suggestions so far:
- Double the time of the daily
that would be in conflict with the definition of a daily standup as written on https://www.scrum.org/resources/what-is-a-daily-scrum . I am strongly against that.
- Have a 5 minute break between infra and dev daily
My specific proposal was shifting the dev daily back 5m so 0940-0955. this leaves a gap of 5m between infra+dev dailies for explicit cuts, grabbing a beverage or short after-daily discussion but still leaves a gap of 5m to any next meeting at 1000Z
- Merge topics and have one daily, 15 minutes total with time for follow-ups after
See also the conversation in Slack
That's in conflict with #174442
So for me that only leaves the shift dev daily by +5m
- Assignee changed from livdywan to gpathak
- Parent task set to #174442
I observed that team members sometimes starts explaining about their respective tasks and also sometimes discuss tasks which are not visible in the infra or dev backlog - In-progress, blocked and feedback.
In my opinion every team member should just talk only about:
- Current progress of the ticket and today's plan for resolving the ticket e.g.
- created a MR and is under review
- discussing with xyz about abc for task resolution
- will be doing ... / ... is needed to finish the task
- Any blocker or dependencies within team members for the task. If urgent, call for help/suggestions in a separate call after the dailies are over or schedule a 15 minutes google meet call with respective team members
- Any external blocker or dependencies not within our team, such as waiting on JIRA SD or boo tickets and status about the tickets
- Status changed from Feedback to In Progress
- Assignee changed from gpathak to okurz
Discussed in QE Tools coffee break 2025-01-27. We decided to run the experiment to shift the dev daily back by 5m. I will update the wiki
- Copied to action #176205: [retro][experiment] Avoid running overtime in our daily standups - 5m break between dailies size:S added
- Status changed from In Progress to Resolved
We have decided for one experiment: #176205
Also available in: Atom
PDF