>This isn't unique to software. It isn't even unique to white-collar jobs. Why does that even need a name?
Kanban originates in Toyota's factory line. The key thing isn't the existence of the list, it's in making people responsible for maintaining and tracking the list rather than consolidating the authority in foremen who direct minions on what to do next. This makes it possible for teams to set priorities collaboratively and move between roles fluidly.
It also establishes a clear order in which things need to be done and an agreed upon subdivision of tasks that make it possible to track the status of work.
Kanban originates in Toyota's factory line. The key thing isn't the existence of the list, it's in making people responsible for maintaining and tracking the list rather than consolidating the authority in foremen who direct minions on what to do next. This makes it possible for teams to set priorities collaboratively and move between roles fluidly.
It also establishes a clear order in which things need to be done and an agreed upon subdivision of tasks that make it possible to track the status of work.