-
Notifications
You must be signed in to change notification settings - Fork 3
3. FAQs
The dataset currently goes as far back as 1st January 2017 for the date and issues tables.
Lead time measures the total time elapsed (in calendar days) from the creation of an issue to it being closed.
Lead time measures the total time elapsed (in calendar days) from the creation of an issue to it being closed.
Changing the forecasting visuals is relatively simple to do. Reasons for this could be if you don’t have ‘enough’ data yet but have a reasonable amount, or if you need to "throw away" old data. Just change the 'Input data range' number for the number of weeks worth of data you do want to use. Watch the % stability though!
This isn’t actually true, and a common myth:
-
With 5 samples we are confident that the median will fall inside the range of those 5 samples, so that already gives us an idea about our timing and we can make some simple projections (Source: Actionable Agile Metrics For Predictability)
-
With 11 samples we are confident that we know the whole range, as there is a 90% probability that every other sample will fall in that range (see the German Tank Problem). Knowing the range of possible values drastically reduces uncertainty