Some people use the word "agile" as a noun, supposedly taking inspiration from the "manifesto for agile software development". -- In this sense, 'kanban board'

Some people use the word "agile" as a noun, supposedly taking inspiration from the "manifesto for agile software development". -- In this sense, 'kanban board' just means "todo list arranged in columns". A description of kanban (as applied to software development) that I did like was what it wanted to emphasise: 1. Maximize flow. - If work flows, there's more assurance that work will get done. 2. Minimize work in progress. Either a worker is working on something, or they're idle. Either a task is being worked on, or it's not making progress. 3. Visualise work in progress. - If many tasks aren't seeing progress, then visualising the work in progress is a way to show the bottlenecks in a process, which might restrict flow. (e.g. do reviews take too long, or are blocked on some key person; some key stakeholder needed for some review or some deployment, etc.). I think if no constraints are put on picking up work in progress, then a kanban board is just a todo list with columns.