Kanban for software development is a newer kid on the block, at least in the US. Besides being just another word like Scrum that is not commonly understood in the English language, how does it stack up? Both Kanban and Scrum align with the well with the value system described in the Agile Manifesto. And they make an interesting pair.
As much as we love scrum, even we would have to admit that it’s not perfect. The main idea of KanBan is very simple and based on the Lean “pull,” “Just in Time” (JIT), and “reduce inventory” principles: eliminate planning inventory by making sure that you don’t commit to doing work until you are actually ready to start the work.
There are an increased number of posts about agile adoption not working out for some folks in larger companies. As the numbers of scrum / agile implemenations sky roket so too will the number of stories where agile is not succeeding.
