We all experience roadblocks while we are sprinting that takes us away from our sprint work. Especially those of us in small shops where we do the development and production support. What is the best tool or method to capture those roadblocks?
Thanks for the answers. What I have ended up doing is creating a generic project called system admin (SA) Then I create an epic for each sprint and instead of asking my team to create roadblocks under the proper projects I have them create subtasks within the epic and tag the issue with the true project it belongs to.
This allows me to monitor on the work board and track all roadblocks. We can also assign point values so we can determine what the effect was on our sprint. Doing this as an epic with points on the sub-tasks does not raise our sprint points and does not effect our velocity calculation.
One option that may work is using the right-click 'Add Flag' option within GreenHopper. This will add a flag to an issue or sub-task and also allow you to query those issues via jql using a query similar to "project = <project name> and Flagged is not EMPTY".
Put it on the whiteboard or wall. The key is not the tool that you use but whether people talk about it, aware about it, and act on it.
I know you could be looking for a GreenHopper's answer, but that's really the best answer for:
What is the best tool or method to capture those roadblocks?
Atlassian released a security advisory on 3/20/2019. The full advisory is here: https://confluence.atlassian.com/doc/confluence-security-advisory-2019-03-20-966660264.html In a nutshe...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs