undefined | Better HN

0 pointsmarcosdumay3y ago0 comments

> "do everything, all at once, and we need right now. Stop doing what you're doing, do this thing instead!"

Hum... Since the single main stated goal of kanban is to minimize WIP, it's safe to say that this is not kanban.

Of course, it won't stop bad managers from implementing it. But nothing will stop bad managers from implementing it anyway. Anything can devolve into that, trying to implement something different won't save you.

0 comments

the_af3y ago

> it's safe to say that this is not kanban

But that's the problem with agile.

Nobody can or wants to pin it down. When it fails, "you are not doing it properly". The stated goals are iterations, early feedback, people over processes... except when they aren't.

marcosdumayOP3y ago

Hum, no. If you go calling some infinite WIP generating process by the name that has as the one most important principle "no matter what you do, keep WIP down", it's you that are bastardizing the language.

the_af3y ago

> Hum, no

Um, yes.

I'm sorry, but the "Agile works, it's just that you are doing it wrong" line of argument is weak and unconvincing. The theory of a methodology means little when there is no buy-in from stakeholders, as is often the case. They reinterpret it to mean whatever they want it to mean. If you haven't struck this wall, then congrats! Most of us in software have to deal with it, though.

hirvi743y ago

> WIP

Do you mind defining this?

mgkimsal3y ago

Work In Progress, I think they're referring to.

marcosdumayOP3y ago

Yep, work in progress.

WorldMaker3y ago

"Work in Progress".

"Strict" Kanban is about minimizing in flight stuff that you don't have bandwidth for. (Strict "traffic limits" based on team size in any specific column.)

hirvi743y ago

Thank you for the clarification, but I am afraid you lost me at this part:

> "Strict" Kanban is about minimizing in flight stuff that you don't have bandwidth for. (Strict "traffic limits" based on team size in any specific column.)

What is "in flight stuff" and "traffic limits?" Are you saying strict Kanban minimizes the number of tasks that are in progress in order to prevent overloading the team i.e., there is an upper limit set to curtail the amount of simultaneous tasks?

3 more replies

j / k navigate · click thread line to collapse

0 pointsmarcosdumay3y ago0 comments

> "do everything, all at once, and we need right now. Stop doing what you're doing, do this thing instead!"

Hum... Since the single main stated goal of kanban is to minimize WIP, it's safe to say that this is not kanban.

0 comments

the_af3y ago

> it's safe to say that this is not kanban

But that's the problem with agile.

Nobody can or wants to pin it down. When it fails, "you are not doing it properly". The stated goals are iterations, early feedback, people over processes... except when they aren't.

marcosdumayOP3y ago

the_af3y ago

> Hum, no

Um, yes.

hirvi743y ago

> WIP

Do you mind defining this?

mgkimsal3y ago

Work In Progress, I think they're referring to.

marcosdumayOP3y ago

Yep, work in progress.

WorldMaker3y ago

"Work in Progress".

"Strict" Kanban is about minimizing in flight stuff that you don't have bandwidth for. (Strict "traffic limits" based on team size in any specific column.)

hirvi743y ago

Thank you for the clarification, but I am afraid you lost me at this part:

> "Strict" Kanban is about minimizing in flight stuff that you don't have bandwidth for. (Strict "traffic limits" based on team size in any specific column.)

3 more replies

j / k navigate · click thread line to collapse