nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the best way to deal with "impediments" in the Kanban board using Jira Software?

Vitor Lima_744tbv

How should the column for impediments be defined, what to do when an impediment happens? Which stage should I return to? Once an impediment is released, how can you know that it can proceed?

Comments

Tara L Conklin

Hi @Vitor Lima

A few suggestions.

Create a column "Impeded" or "blocked" ( I infer from your question you already have this.

I'm sure you know this, but for future reference, I'll quickly review impediments.

Impediments are anything that can stop the progress of a Jira ticket or prevent it from getting finished. This can be so many things but common ones;
- a tool, server or database necessary for the work goes down.
- unexpected dependency is identified and the ticket can't move forward until the dependency is addressed.
- personnel or customers essential to completing, QAing or approving the work is unavailable.
I recommend creating a separate status "impeded" or "blocked" in the workflow and adding that status to the "Impeded" column. This will allow you to move that ticket to that column. Other statuses to consider:
- pending
- escalated
In the Impeded status screen perhaps consider adding new fields for
- the team or person the ticket has been escalated to.
- the date escalated/reported/impeded (whichever)
Keep diligent comments/notes about when and to whom it was escalated, follow-up, and ultimately resolved.
Once there is confirmation the impediment is resolved and the ticket can move forward, just move the ticket from the "impeded" column back to the column which accurately reflects its proper state.

I'm a big proponent for fields and statues instead of relying on labels and comments. Labels and comments are easily ignored or overlooked. It's important to keep track of when a ticket is impeded when it was impeded and who is accountable for resolving it.

I hope this helps!

Tara Conklin, CSM

Vitor Lima_744tbv

Thank you Tara

Tara L Conklin

Happy to help @Vitor Lima

M Vijay Kumar

Hi Tara,

But how do you know in which status the User Story has an impediment if we choose to have a Separate Status?

Thanks,

Vijay

Vijaya Lakshmi_aoi4lt

Why cant we use the Impediment flag in the respective status... this is an inbuilt functionality isnt it ?

Using flag is the right way of managing your blockers and impediments. it will help you identify in which status you are currently blocked and also with the ticket highlighted in different color it is very visible on the board

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

agile

kanban