action #179966
closed
[tools][organisational] Team split - additional scrum master size:S
Added by okurz about 2 months ago.
Updated 24 days ago.
Description
Motivation¶
With two teams "dev" and "infra" we should also have separate scrum masters.
Acceptance Criteria¶
-
AC1: there can only be two scrum masters
-
AC2: all relevant places mentioning tools team scrum master clearly state individual teams and their respective Scrum Master
Suggestions¶
- Copied from action #179963: [tools][organisational] Team split - split backlog queries added
- Description updated (diff)
- Assignee set to tinita
- Priority changed from Low to Normal
- Target version changed from Tools - Next to Ready
- Priority changed from Normal to High
- Status changed from New to In Progress
We did not have a chance to estimate it but this is de facto in progress.
livdywan wrote in #note-4:
We did not have a chance to estimate it but this is de facto in progress.
See #167884#note-10
- Due date set to 2025-04-23
Setting due date based on mean cycle time of SUSE QE Tools
Discussed it briefly.
Many ideas floating around of what we can split but also no need to decide right now. Let's take it step by step. I think we're on the same page here.
- Let's ask people in the team if they'd like to add their dev/infra preference to the wiki
- Everyone can choose where to participate. and they can also change it, say, work on dev topics for a week or two and then go to infra or vice versa.
- Do we want separate team chats?
- Right now it is easy to move between teams, and it can be beneficial to communicate topics that concern infra and dev. A separate team chat might come at the cost of some of that immediate feedback
- Noise of the team chat is largely impacted by notifications. #179275 covers test failures which could be relevant for either team.
- Keeping track of who checked in for the day, SLO's, tickets not updated, due dates in general so far fall back to Liv. It would make sense for Tina to specifically cover those for dev topics. That said, Liv is still happy to check all tickets in so far as they've not been covered.
- This is a time-limited experiment. We can roll back and we can change it.
- Subject changed from [tools][organisational] Team split - additional scrum master to [tools][organisational] Team split - additional scrum master size:S
- Description updated (diff)
- Copied to action #180758: [tools][organisational] Team split - proper team roster documentation size:S added
- Description updated (diff)
- Also confluence squad page and any other relevant places but without duplicating more QE Squads Structure
Done.
- This is a time-limited experiment. We can roll back and we can change it.
Added a more explicit note to the wiki. Tina only agreed to 6 weeks to start with and is free to re-consider after that.
- Let's ask people in the team if they'd like to add their dev/infra preference to the wiki
- Everyone can choose where to participate. and they can also change it, say, work on dev topics for a week or two and then go to infra or vice versa.
- Do we want separate team chats?
- Right now it is easy to move between teams, and it can be beneficial to communicate topics that concern infra and dev. A separate team chat might come at the cost of some of that immediate feedback
- Noise of the team chat is largely impacted by notifications. #179275 covers test failures which could be relevant for either team.
See also #180758. Not on the backlog for now since we don't know if that is what we want.
- Status changed from In Progress to Feedback
livdywan wrote in #note-8:
- Let's ask people in the team if they'd like to add their dev/infra preference to the wiki
https://suse.slack.com/archives/C02AJ1E568M/p1744195172220009
Several people expressed their preference in the wiki now.
Keeping track of who checked in for the day, SLO's, tickets not updated, due dates in general so far fall back to Liv. It would make sense for Tina to specifically cover those for dev topics. That said, Liv is still happy to check all tickets in so far as they've not been covered.
We do not strictly separate this at this point. As I said that's fine by me.
@tinita if I didn't miss anything we can resolve this. Otherwise i'm available for a quick text or audio chat to clarify.
- Status changed from Feedback to Resolved
@tinita if I didn't miss anything we can resolve this. Otherwise i'm available for a quick text or audio chat to clarify.
ok, thanks for updating.
- Due date deleted (
2025-04-23)
Also available in: Atom
PDF