Project

General

Profile

Actions

action #152957

closed

coordination #127031: [saga][epic] openQA for SUSE customers

coordination #152955: [epic] Metric-driven project management in SUSE QE Tools team

Weekly evaluation of cycle-times within SUSE QE Tools size:S

Added by okurz 4 months ago. Updated 2 days ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
2023-12-28
Due date:
% Done:

0%

Estimated time:

Description

Motivation

We already have cycle times e.g. from #121582 and in #127025 we want to improve the numbers we have available but in our usual work the metrics do not have an impact. So we should ensure that we establish a use of cycle times in our usual processes, e.g. bring them up in a weekly meeting, discuss in chat, dailies, etc.

Acceptance criteria

  • AC1: Cycle times of tickets are used in at least one way regularly within our team

Suggestions

  • DONE Have periodic evaluations of our metrics e.g. cycle time, like in a regular call chat conversation, existing or newly organized e.g. the estimations or the coordination
  • https://monitor.qa.suse.de/d/ck8uu5f4z/agile?orgId=1&refresh=30m
    • DONE Document in the wiki where to find out metrics graph
    • What about the median value? We are fine with the mean value that we have for now
  • Wrt cycle time see also How we work on our backlog
  • Document a memorable short explanation what cycle time means to us, how to read the graph
  • Ensure that we really do talk about the metrics and ensure they have an effect

Related issues 1 (0 open1 closed)

Related to QA - action #127025: [tools][metrics] Improve cycle + lead times in GrafanaResolvedokurz

Actions
Actions #1

Updated by livdywan 3 months ago

  • Description updated (diff)
  • Status changed from New to Workable
Actions #2

Updated by okurz 3 months ago

  • Status changed from Workable to Blocked
  • Assignee set to okurz

We did not finish estimating but wanted to block on #127025

Actions #3

Updated by okurz 3 months ago

  • Related to action #127025: [tools][metrics] Improve cycle + lead times in Grafana added
Actions #4

Updated by okurz 3 months ago

  • Status changed from Blocked to New
  • Assignee deleted (okurz)

#127025 resolved. https://monitor.qa.suse.de/d/ck8uu5f4z/agile?orgId=1&refresh=30m&viewPanel=4&from=now-6M&to=now now shows results that should be useful and helpful for the team

Actions #5

Updated by livdywan 3 months ago

  • Subject changed from Weekly evaluation of cycle-times within SUSE QE Tools to Weekly evaluation of cycle-times within SUSE QE Tools size:S
  • Description updated (diff)
  • Status changed from New to Workable
Actions #6

Updated by livdywan 3 months ago

  • Description updated (diff)
  • Status changed from Workable to In Progress
  • Assignee set to livdywan
Actions #7

Updated by livdywan 3 months ago

  • Description updated (diff)
  • Status changed from In Progress to Feedback

Some thoughts:

  • How we work on our backlog mentions the due-date is set automatically to 14 days in the future as soon as a non-low ticket is picked up. That period is roughly the median cycle time
    • The presumed median cycle time could be validated whenever we discuss metrics
    • Ideally tooling can compute the actual median cycle time based on priority.
    • Due dates should ultimately be set based on the actual median cycle time.
  • Have periodic evaluations of our metrics e.g. cycle time, like in a regular call
    • We already look at achievements in the coordination call and consider how we're doing. Looking at metrics would make sense.
    • I'm thinking we can look at metrics in the coordination call and consider follow-up tickets, similar to how we do it in the retro when we run out of time.
  • Document a memorable short explanation what cycle time means to us, how to read the graph
    • cycle time: The total elapsed time to complete an operation or set of operations. from wiktionary
    • Perhaps the best way to define how to read the metrics is to discuss them, and document what we learn from them?
Actions #8

Updated by okurz 3 months ago

  • Due date set to 2024-02-16
  • Priority changed from Normal to Low

wiki extended and we will conduct as you suggested in coordination calls. Tracking as low with according due date.

Actions #9

Updated by okurz 2 months ago

  • Due date changed from 2024-02-16 to 2024-02-27
Actions #11

Updated by livdywan about 2 months ago

  • Status changed from Feedback to Resolved

Cycle times were discussed in the last Fortnightly Coordination and they are a documented part of the agenda. So we can probably consider this resolved.

Actions #12

Updated by okurz 2 days ago

  • Due date deleted (2024-02-27)
Actions

Also available in: Atom PDF