tag:blogger.com,1999:blog-1423003429632694999.post3023546170996244211..comments2024-03-28T07:02:38.565+01:00Comments on Lean und Kanban: "Kanban does not work for XY"Arnehttp://www.blogger.com/profile/15740341452041610643noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-1423003429632694999.post-75841204015828936862012-05-06T12:31:13.873+02:002012-05-06T12:31:13.873+02:00It's probably not CONWIP but the matter that o...It's probably not CONWIP but the matter that often one person is working alone on one ticket across the board. So there are no hand-offs and pull is only done from the input queue. Happy to read that you agree in opinion :-)<br /><br />Cheers,<br />KlausAnonymoushttps://www.blogger.com/profile/09302393758668382467noreply@blogger.comtag:blogger.com,1999:blog-1423003429632694999.post-73889350022744338852012-05-06T12:18:21.671+02:002012-05-06T12:18:21.671+02:00Hi Klaus,
thanks!
I don‘t consider CONWIP not to ...Hi Klaus,<br /><br />thanks!<br />I don‘t consider CONWIP not to be real pull. Why should it?<br />For me the most important thing is: Did the team get the message about evolutionary change and does it improve? If the answer is yes, I think it‘s perfectly fine if they start with a weather shallow Kanban implementation and improve very slowly.<br />And yes, it‘s a good topic for #klrat :-)<br /><br />Cheers,<br />ArneArnehttps://www.blogger.com/profile/15740341452041610643noreply@blogger.comtag:blogger.com,1999:blog-1423003429632694999.post-89543887852727920192012-05-06T12:15:22.872+02:002012-05-06T12:15:22.872+02:00Henri,
as I mentioned: The team does not want to ...Henri,<br /><br />as I mentioned: The team does not want to improve, or the process does not suffer from overburdening or unevenness in flow (which I‘ve never seen).<br />And there might be one more situation: If there‘s really high pressure to change very rapidly, Kanban might be to slow. If an organization has to choose between revolution and death, I probably would‘t recommend Kanban.<br /><br />Cheers,<br />ArneArnehttps://www.blogger.com/profile/15740341452041610643noreply@blogger.comtag:blogger.com,1999:blog-1423003429632694999.post-30414027757864658922012-05-06T10:48:54.322+02:002012-05-06T10:48:54.322+02:00I really like your post! There is one more topic: ...I really like your post! There is one more topic: is kanban on team level (e.g. specialist teams like QA or support) kanban or personal kanban. They are primarily handling tasks on their board and usually only have a CONWIP system where no "real pull" is possible which smells like personal kanban. Nevertheless, they usually also have metrics in place, perform continuous improvements, do queue replenishments, etc. which are important elements of kanban. And even more important, they follow incremental, evolutionary change which is part of the Kanban method. I see it also very often that other departments (specialist teams) join their board sooner or later. So for me it's definitely kanban what they are doing. What do you think? I think, I'll address this at #klrat ;-)Klaus Leopoldhttp://www.klausleopold.comnoreply@blogger.comtag:blogger.com,1999:blog-1423003429632694999.post-75270927602748865282012-05-06T09:33:50.003+02:002012-05-06T09:33:50.003+02:00Thanks, an interesting read. You stage that Kanban...Thanks, an interesting read. You stage that Kanban is not good for certain situations. Do you have examples on those envinronments?Henri Sorahttp://blog.ambientia.finoreply@blogger.com