0

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?

Victor Grazi
  • 241

1 Answers1

4

Don't have a separate column. I know it's an example used everywhere but it's more geared at highlighting waste between steps, the TDD cycle is pretty tight.

I'd recoummend Development column with sub column Dev Active and Dev Done. Then next would be Demo Active and Demo Done, Prod Deploy Active Prod Deploy Done. What this let's you see is how much time is wasted in the Dev Done column because your PO is unavailable for Demo etc.

For functional tests etc you can set a policy for the column, it can't move into Dev Done until Functional Tests have been written and are passing etc.

danswain
  • 141