How to account for time for different stages of a task within a kanban?

Question

Agile

Colleagues, we want to launch (in Jir'e) a kanban board for tracking tasks.
The question arises with planning the required time for different stages of the task (analysis - development - testing). Because the time tracker in Jir is the same for the task, it is impossible to divide how much time is scheduled for each stage - only the amount.
If you don’t bother with dividing time into stages at all, but only a general plan / fact, you won’t be able to evaluate the effectiveness of individual specialists, which is also not good ...
Or lower all this to the level of subtasks ...
Has anyone solved a similar problem?

Answer 1

Kanban does not imply a lot of task scheduling functionality (unlike Scrum), but is primarily aimed at optimizing the work process (minimizing the number of tasks in work, optimizing the average time to complete one task, but here a limitation appears - the tasks should be approximately the same ).
The execution time is estimated as a whole for the task, plus the planned time can optionally be set.
Accordingly, the task set cannot be solved within the framework of the standard Kanban.

Answer 2

In those projects that I lead, the total scope of work is often not very clear initially.
It is difficult to say how long the design will take until the technical specifications are made, before the design is drawn it is difficult to say how long the layout and backend will take, etc.
Therefore, I create this clearly with separate tasks, the first stage has a clear deadline, I fill all subsequent stages of estimate very roughly and with a margin. As the previous stages are closed, I will update them.
In principle, you can enter this as subtasks in some kind of story, a matter of taste.
PS Personally, the scrum board seemed more convenient to me.
However, the differences are not fundamental.

Answer 3

analysis - development - testing - these are not stages of tasks, but full-fledged tasks.
Use projects for parts of your work.
Divide projects into epics (what you call a task is an epic).
And already analysis - development - testing - tasks. And they can have subtasks if they take a lot of time (roughly speaking, more than a day).
And do not forget that strong control reduces the developer's motivation (and, as a result, productivity): the developer wants to develop, not "shift papers".
Lack of control also reduces productivity.
Therefore, it is necessary to choose the golden mean.

Answer 4

If fat is not a sacred cow, you can look at projectscloud.ru - there is a kanban board there, very functional (and there is a free plan).