Short, informal, and they could've used a copy editor, but you can hardly beat the price, and I did enjoy reading it.

This is a lightweight introduction to both kanban and scrum development methodologies in the form of a comparison/contrast essay that spells out the essential assumptions of each, plus a case study. The goal seems to be to give you a rough idea whether one, both, or neither is suitable to your situation, and to serve as an introduction to your own experimentation and further research. ( )

This is a great little book that introduces Kanban ideas of those who are already committed to aspects of Scrum. If your team finds that it has too many uncompleted stories in your iterations, you should consider Kanban, which puts a limit on how many stories can be WIP at any one time. If the number of stories that are WIP goes below the limit, the team can put more members on those remaining tasks to finish them off. By this means, Kanban is self-regulating, depending on strict limits about the influx of stories and how many can be in process.

That's all in the first half -- the theory, with some great illustrations comparing Scrum and Kanban boards, and how they can be integrated.

The second part is a case study of an operations group that moved to Kanban with small multi-speciality teams, each with one point person to handle a specific internal customer's requests. It seems like a nice setup for addressing IT needs of far-flung parts of an organization.

The thing that keeps me from giving this a 5 is that it's only 104 pages and a bit lite. Another case study would be helpful.
( )