Having said that, the human side does seem to be an important piece that probably needs making more explicit. I’m undecided about how, or if, Kanban treats this differently to XP and Scrum though.

Stop and notify behaviour seems independent from visualisation and limiting WIP. The other aspect of jidoka, separating human and machine work, ends up being more about what we automate and what we do by hand.

I raise the point because I think it should be explicit.

By Cadence I mean the team policies around when they will perform various activities such as prioritisation, planning, reviewing, releasing, retrospecting. These could all be at varying intervals, and generally form a regular rhythm. It’s possible for the cadence to be
irregular, although I suspect this will only work for very small teams with less need for more formal co-ordination.

Karl