In Kanban JIRA board we use Pull methodology, how to identify urgency of task and customize board

[Rpar13]

we have developed new Kanban board where color coding and all the process are set up for the user story, including all the statuses including inProgress...to Done.

Difficulty is that if we have multiple  task that has created and we are utilizing the  pull methodology for the development/review or any....prospective.

How to differentiate on Kanban board with any urgency to accomplished the task ?

Is there any way to indicate the task is High/Medium/low Priority on JIRA kanaban board  ?

So anyone can pull those task as priority and accomplished in order to severity...

Thanks 

[Rpar13]

Our Kanban board doesn't seems that way set up that 'Everyone should be working "top-down" which means you're always working in priority order" 

Is there any other solution where we can indicate that this are high priority or Lower ?

[Warren]

Hi @Rpar13

If you're "using" Kanban via a Kanban board, then it's implicit the the items are prioritised. If yours aren't prioritised, then you should invest some time in doing it - it will be worth it in the long run.

See this or many other articles on how to use a Kanban board correctly

[Rpar13]

Thank you for the guidance. just curious how to streamline in JIRA - prioritized task any tips and trick that it shows first in order to pick ( like any filter or option to choose).

I gone thru the article : which is asking to get us kanaban tool ? 

Solution: How to prioritize your development process in JIRA itself.

With Kanban you can deal with all the prioritization issues you’re facing, in a surprisingly easy way. Instead of prioritizing, by giving labels (low, medium, high), order tickets by priority — in the backlog/to do column — from the top to the bottom.

Problem solved! Really? Let’s examine:

PO can simply reorder tasks on the board at anytime when priorities change. That way he is in control.

Even better, If you have a physical Kanban board the whole team can instantly see the change in priorities. Boards are very cheap and a valuable Kanban tool. Get one!

There is no need to use labels and no issues with team not delivering high priority tasks. The team can manage itself. No need to ask the product owner anymore.

[Warren]

The idea that I wanted you to see from that article is that you need to prioritise the issues on your board - nothing more really.

You shouldn't need a filter or anything else, because the priority will be obvious.

If you have 4 prioritised items on the board :

2 (in progress)

4 (in progress)

1 (to do)

3 (to do)

If another developer needs to start something, they will choose item 1 because it's next.

If item 5 is being added and it is really important, it can be added after 4, so :

2 (in progress)

4 (in progress)

5 (to do)

1 (to do)

3 (to do)

so that item 5 would be the next one to start.

You can also have an "expedited" lane for very urgent items

[Warren]

Hi

A Kanban board is essentially a prioritised list of items, so the top item is the highest priority. Everyone should be working "top-down" which means you're always working in priority order.

Hope this helps