I am wondering how to construct a Kanban and generate meaningful cumulative flow diagrams in a scenario where steps are not required to be performed in the same order.
As an example, we might have columns "Development" followed by "Write-tests". But some developers write their tests first, in a "test-driven" or "behavior-driven" way.
I can make the workflow accommodate flow in either direction, but the resulting CFD will be skewed.
I could also merge the dev and test into a single column, but they are really different value-adds and the resulting cards would be larger than I want them to be.
Is there a Kanban way of handling such scenarios?