action #121612
closed
[tools][experiment] split dev/infra work management within tools team for better focus size:M
Added by okurz about 2 years ago.
Updated almost 2 years ago.
Description
Motivation¶
We have too many sagas on our plate meaning not enough focus. Let's try to focus our dev/infra focussed team members better for limited time for better focus while keeping processes that still benefit everyone
Suggestions¶
- In the time range 2022-12 - 2023-02 split the dev/infra work management with separate backlogs and calls where it makes sense, e.g. separate daily, separate estimation, separate unblock
- Still keep the weekly&retro together because those are good synchronization points
- Most work for keeping both sub-teams under control would fall onto PO+SM
- Description updated (diff)
- Subject changed from [tools][experiment] split dev/infra work management within tools team for better focus to [tools][experiment] split dev/infra work management within tools team for better focus size:M
- Status changed from New to Workable
- Assignee set to livdywan
We probably don't need to estimate this since it's a coordination task. I suggest we discuss it as part of the retro this week and decide on concrete experiments to run.
Feel free to add suggestions here ahead of the call, though. Or just think about what would help you and bring it up on the call.
My suggestion:
- a daily call for infra-mgmt 1015-1030 including covering "unblocking+estimating"
- usual daily+unblocking+estimating in the usual slots w/o infra tasks
- Project changed from 46 to QA (public)
- Project changed from QA (public) to 46
- Target version deleted (
Ready)
okurz wrote:
- a daily call for infra-mgmt 1015-1030 including covering "unblocking+estimating"
nsinger prefers a later time, I offered 1300
- Project changed from 46 to QA (public)
- Target version set to Ready
- Status changed from Workable to Feedback
We discussed it in the retro. An exact split between tickets hasn't been decided yet, instead this will be evaluated as part of this experiment e.g. by excluding infra tickets from the estimations call. It's also left open to everyone to consider joining the infra work. I'm sending out invites for the new slot and updating the wiki accoringly.
I added two split backlog views to https://progress.opensuse.org/projects/qa/wiki/Tools#How-we-work at the end of the section. I am in the process to add the "infra" tag to each ticket that belongs to infrastructure work. The "openQA infrastructure" project alone does not cut it as we have a lot of not-openQA infra work.
I realized I didn't add any notes here recently.
There was some feedback in daily standups. Attendance in both calls is a bit in flux at the moment, sometimes more, sometimes fewer people in both calls. The infra daily tends to be more brief. Some people are definitely interested in both.
Overall vibe is good and we'll continue to see how things evolve.
- Due date set to 2023-03-24
We discussed about this and made the observation that infra-related management is more focussed and excluding dev-discussions but we still hear about infra-topics in dev-focussed calls more. Let's try for the next time to artificially over-focus on separating the discussions.
- Due date deleted (
2023-03-24)
- Status changed from Feedback to Resolved
Discussed in retro 2023-03-17 and we decided that our team structure is good as it is with the split. At any time in the future we can of course change that again.
Also available in: Atom
PDF