action #152957
Updated by livdywan 3 months ago
## 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 cycle times of tickets are used in at least one way regularly within our team ## Suggestions * 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 * Document in the wiki where to find out metrics graph * ~~What ~What about the median value?~~ value?~ We are fine with the mean value that we have for now * Wrt cycle time see also [How we work on our backlog](https://progress.opensuse.org/projects/qa/wiki/Tools#How-we-work-on-our-backlog) https://progress.opensuse.org/projects/qa/wiki/Tools#How-we-work-on-our-backlog * Document a memorable short explanation what cycle time means to us, use, how to read the graph * Ensure that we really do talk about the metrics and ensure they have an effect