How do you obtain a ”perfect flow” of work tasks passing through your software development team? That question have been in my head for quite some time. I can start by admitting that I don’t have a solid answer to that question (yet). However, I have instead thought of a way to visualise if you are having ”perfect flow” or not. How? I’m thinking of a tachometer!
Tachometer to find perfect flow
First of all, this is just an idea that popped into my head (this is actually the first encounter with the ”outside world”, so please bear with me). The idea is however to use a tachometer to indicate ”perfect flow” on a kanban board for a development team. Just like a tachometer is indicating if you are using the sweet-spot of your engine at any given moment.
My little example is a kanban board with three columns:
- Design – Given the value 1
- Development – Given the value 2
- Test – Given the value 3
The values are used to calculate the position of the needle in the tachometer. I will now give you three examples that hopefully explains it all!
Example 1 – ”Too early”
In this example three tasks are in the ”Design”-column, giving a ”tachometer value” of:
1 + 1 + 1 = 3
Thus indicating that we are ”too early”, and that the later steps in the flow (”Development” and ”Test”) are not utilised. The analogy with a car would be to ”gear up” meaning that the team needs to take the ongoing tasks to the later steps of the process.
Example 2 – ”Too late”
In this example three tasks are in the ”Test”-column, giving a ”tachometer value” of:
3 + 3 + 3 = 9
Thus indicating that we are ”too late”, and that the team soon will run out of things to do. The similarities with a car would be to ”gear down” and for the team to put focus on feeding in new tasks to the kanban board.
Example 3 – ”Perfect flow”
In this example the three tasks are evenly spread between the columns, giving a ”tachometer value” of:
1 + 2 + 3 = 6
Thus indicating that we have a ”perfect flow”, and that the steps in the process are utilised in the best possible way!
I understand that the mathematical formula behind this idea must be improved if this should become a reality. There are also cases where a tachometer like this will not be useful, for example if the team has just started. Maybe this can act as a challenge to manufacturers out there of digital kanban tools to add a tachometer in their product!
All the best,
Tomas from TheAgileist