New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add feature: WIP limits #783

Closed
xet7 opened this Issue Feb 6, 2017 · 7 comments

Comments

Projects
None yet
4 participants
@xet7
Copy link
Member

xet7 commented Feb 6, 2017

Moved to here from wefork#86

Originally asked by @denisz1

Doing Kanban without WIP limits isn't easy. Please add WIP limits, it's really essential.

"WIP limits" are central part of LEAN process - a team doing LEAN (or Kanban etc.) needs them. Otherwise kanban board is just a pretty thing without real management power.

Very good info is many explanation videos on YouTube.
This one is very good, I linked to the exact time 28:12 in the video.
Short one

There are plenty of explanations. Just search "kanban wip limits", and maybe:
JIRA has it
More
More

@xet7 xet7 added the Feature label Feb 6, 2017

@grokky1

This comment has been minimized.

Copy link

grokky1 commented Mar 14, 2017

Agree we also use WIP limits, but since wekan doesn't have it, we duplicate some of the board on our physical whiteboard, and write the WIP limits manually. Sucks I know, but important.

@amadilsons

This comment has been minimized.

Copy link
Contributor

amadilsons commented Sep 28, 2017

@xet7 any idea of how the layout for this feature should look like?
Maybe "WIP Limit {{ limit }}" beneath the list title and the option to edit it in List Activities popup? What do you think about that?

@grokky1

This comment has been minimized.

Copy link

grokky1 commented Sep 28, 2017

@amadilsons I think it should be similar to how it's used elsewhere.

I think that maybe "WIP Limit (3)" is too "wordy". It should simply have the number next to the name, for example:

Backlog (*) | Ready (6) | In-progress (3) | Testing (3) | Complete (*)

Or something like that. The "(*)" is optional / unnecessary.


But there is another questions to consider:

Should user be allowed to add more tasks than allowed for that column? So if the WIP limit is 3, can user add 4 tasks? If yes, then some tools show it in red e.g. "4 of 3". If no, then user cannot add a task until he clears a task. I think we should have this as an option, as different teams work differently.

To keep it simple for now, maybe we can just ignore this issue.

@amadilsons

This comment has been minimized.

Copy link
Contributor

amadilsons commented Sep 29, 2017

I'm not sure the user should be allowed to add more than the limit. Wouldn't that defeat the purpose of the WIP limit?
But I also agree it should be an option!
For now, I'll go for a simpler version of this feature, not allowing the user to add more tasks than the limit.
After that, we consider solving that issue!

@grokky1

This comment has been minimized.

Copy link

grokky1 commented Sep 29, 2017

@amadilsons I agree - in our team we never add more tasks than the limit!!! Like you said it defeats the purpose!

@synergico

This comment has been minimized.

Copy link

synergico commented Oct 2, 2017

@grokky1 should it be something like In-progress (0/3) for the limit? It would be rather confusing if only (3) there, people might think it is just the count number.

@grokky1

This comment has been minimized.

Copy link

grokky1 commented Oct 2, 2017

@synergico I've seen it both ways. In my current team we use (3). But in the past I've also seen (1/3).

It depends on the maximum number:

  • in a large team its better to have (11/16) because it's easier than counting the tasks in that column.
  • but in a small team, it represents only the maximum, and the number in progress can be easily counted just by looking at the tasks in that column. So that extra /x is unnecessary "noise".

Ideally it should be a config option - but that means more work. It depends on how much work we should put into version 1 of this feature! 😆

@xet7 xet7 closed this in c346743 Oct 9, 2017

xet7 added a commit that referenced this issue Oct 9, 2017

Merge branch 'amadilsons-issue783' into devel
WIP Limits. Thanks to amadilsons ! Closes #783
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment