I need to setup a Kanban Board where I need to setup a WIP Limit for different items in the Workflow.
So for example, say I have 20 items of which 5 are Bugs, 10 are Major Enhancements and the remaining 5 are Minor Enhancements.
Can I set a WIP Limit on the "Ready for Dev" Status on the Kanban Board like below :
Bugs : 3
Minor Enhancements : 4
Major Enhancements : 1
I read somewhere that this is not possible in Jira. Can you confirm/clarify ?
Hi @Subramaniam Shastri - Welcome to the Atlassian Community!
No, you won't be able to differentiate between the swimlanes with WIP limits - they are set for the entire column.
You could create separate boards for each of those and control your WIP Limits there and then have a master board with everything on it like you already have.
So you are saying build the issue constraints based on different issue types even though the UI in the Board does not have the ability to show it based on Issue types.
That way at least the triggers are being applied even though the Board UI may not necessarily reflect it in the way we want.
Is that right ?
Just copy the current board 3 times. Then change the filter for each board to look something like:
Project = ABC and issuetype = Bug
Project = ABC and issuetype = Major
Then change the WIP Limits for the appropriate columns. The board UI doesn't really change at all other than the WIP Limits.
The last time I think it was in a webinar about the Kanban Maturity Model, basically stating that it is difficult for a company to get past level 3 (6) of the KMM. I know him quite well and he is ranting against Jira for many years.
Just watching Atlassian's Product Managers' videos on Kanban or reading their articles on their blog make me cry. They have no clue what-so-ever.
For me it has always been clear that Jira is a bastardised issue tracking system on steroids. I has nothing in common with a modern workflow management tool.
So why am I here? Because Atlassian has better sales people than product managers. ;-)
Actually I don't think you can even transition from Kanban Maturity Model - Maturity Level 0 "Oblivious" to Level 1 "Emerging" - because that requires personal WiP limits (KMM ref VZ1.1) - which I don't think Jira does either. Nor does it support CONWiP (KMM ref e.g. VZ2.11) which you need at Maturity Level 2. Basically as the above poster is saying Jira doesn't really support Kanban at all. No surprise to hear then that David Anderson is not a fan - he'd be daft to suggest Jira.
If anyone is reading this from Atlassian please note that David Anderson is the "inventor" of the Kanban Method and the author of many influential Kanban books and is generally seen as the authority on Kanban (just in case you hadn't heard of him). I would strongly advise you to read the "Kanban Maturity Model" book. Even just the one chapter on "Visualize" would do and go through the diagrams in that chapter of how people are supposed to set up their boards at different Kanban Maturity levels. You very quickly encounter many required visualisations that Jira simply does not support. Until you fix this we can only shake our heads and look for another tool if we actually want to do Kanban.
There is a new Marketplace app that comes out of a colleague in the Kanban University environment that does all of the things mentioned above.
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events