313
edits
Konstantina (talk | contribs) (creating budget process basis metrics) |
(Warning added) |
||
(4 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
{{Warning |1= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.|title= With effect from 1st September 2023, the Mozilla Reps program was closed and activities ended.}} | |||
{{remonav}} | {{remonav}} | ||
=Overview= | =Overview= | ||
On October 2016 we’ve measured with the help of a script | On October 2016 we’ve measured with the help of a [https://github.com/MichaelKohler/remo-mean-time-approval script] the average time that it takes for a budget request to be approved. | ||
[[File:Screen Shot 2016-11-11 at 16.08.15.png|center|Results from the Budget Process Basis Analysis]] | |||
You can find the full results here | '''You can find the full results [https://datastudio.google.com/u/0/#/org//reporting/0B8afomu5khGpaVJQbmxGOEs4VXM/page/TQy here]''' | ||
Our first goal is to bring down the timing for remo-approval which was set on 7.8 days. Our goal is bringing it down to 5.5 days (roughly 30%) | Our first goal is to bring down the timing for remo-approval which was set on 7.8 days. Our goal is bringing it down to 5.5 days (roughly 30%) | ||
{{admon/important|average for remo-approval|That timing was not set based on the average full data rather on the average we saw on the last 12 months. The reasoning behind this decision is the following: By analyzing the data per month, | {{admon/important|average for remo-approval|That timing was not set based on the average full data rather on the average we saw on the last 12 months. The reasoning behind this decision is the following: By analyzing the data per month, we saw a normality for around 2 years back and then an "uphill" with spikes inside the last 12 months. We realised we needed to bring down that number. }} |
edits