|
As others have noted the definition of kanban comes too late in your article. Also, I think a citation to wikipedia is in order if you're going to copy it and simply expand the initialisms. Regardless, it's not a particularly helpful definition for anybody that's never heard of kanban, and certainly doesn't help anybody familiar with kanban to know what specifically you're evaluating; you need to get everybody on the same page from the outset. Given lack of concrete examples and your previous posting history I would consider this more of an advertisement for your product, to which I've now applied for an invitation, but you seem to be genuinely responding to comments here and nobody else has complained. I suppose either way, well played. I have other comments but I'll hold them until I find out exactly what you mean by kanban, because I've been admittedly self-identifying the process I'm using as kanban and maybe it's not. I will say this much though, the practices of kanban (visualization, limited work-in-progress, managed flow, feedback loops, etc.) are all valuable in my opinion and I wonder which of these you see leading to, or how you see them leading to, the problems you've cited. Also, I wouldn't mind some more concrete metrics to back up such an inflammatory title. |