Survival analysis to estimate kanban tasks completion times I am working on a problem to estimate task completion time in kanban (project management tool).
While doing EDA, I looked at tasks that are either done or cancelled. In this case, I defined the completion time as the time taken from task creation to done/cancelled.
I noticed I am running into an issue with that definition. I am disregarding tasks that have not been done yet. If we think of &quot;task = done&quot; as &quot;event = 1&quot;, this is like throwing away observations with &quot;event = 0&quot; in survival analysis, giving us a biased result.

How should I handle this?
I would also like to get some inputs on how should I approach &quot;done&quot; vs &quot;cancelled&quot;?
It's a matter of defining exactly which problem you want to solve, and there might be many variants:

If the goal is really to estimate &quot;time completion&quot;, then imho you should use only completed tasks, since the other tasks haven't been &quot;completed&quot;. Note that in this case you're counting time actually spent on the task.
If the goal is to estimate &quot;time of solving the task&quot;, whether by completing it or cancelling it, then you're counting the duration between the time the task was initialized and the time it was either completed or cancelled. Note that in this case the duration may include time spent on other tasks.

In both cases above, I don't see any proper way to include tasks which are still pending. My idea for these cases would be to calculate a different statistic, something like &quot;rate of completed tasks after X days&quot; for instance.