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?
Hi @Vitor Lima
A few suggestions.
I'm sure you know this, but for future reference, I'll quickly review impediments.
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
@M Vijay Kumar we had the same issue you brought up and opted to use a label and swimlane to indicate a ticket is blocked in a specific status.
We created a "blocked" label (you could use a component or custom field as well) and then setup a swimlane on the boards to separate out tickets with that label so they were clearly visible on the board.
I found this more helpful than having a separate status/column because you could see from looking at the status if development couldn't start, development couldn't complete, testing couldn't happen, etc. without having to read a bunch of comments. And the ticket would get assigned to whoever was responsible for removing the blocker so there was clear ownership.
Hope that helps!
Hello all! It has been 20 years since the agile manifesto was introduced, and closer to 40 years since software development began moving away from a waterfall-type approach. While many teams have ...
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