RecentlyI've come across a couple of blog posts here and there that suggest there's some sort of debate or controversy about the kanban approach to software development, as if it were in conflict with agile development in some way. Permit me to make a flat statement: There is no such controversy; no such conflict.
The definition of "agile" consists of nothing more than the values and principles expressed in the Agile Manifesto. The authors wisely chose to remain silent about matters such as batch-and-queue operations, iterations, retrospectives, and other details of popular methodologies, thus leaving the door open for creativity, innovation, and improvement. By the same token, there is nothing in the kanban approach that conflicts with any of the values or principles of agile development.