As part of the process of curating a backlog, is there a best-practice method within Greenhopper of denoting (1) whether a new item has been verified as a blocker, and (2) whether a given blocker item has been relatively-ordered vertically by the master (relative to other existing blockers within the backlog)?
Question asked during the August 30th, 2012 webinar titled "Improving Processes with Scrum and Kanban"
The best practice is to have the Product Owner (Master) decide on whether this is a blocker or not. The PO priortises all issues in the Backlog.
One option is to tie bugs to stories, so that you do not close a story unless all the associated bugs are fixed, tested & closed. A Suggestion is to create a Story Bug as a kind of sub task for this purpose.
Thanks for signing up for Jira Ops! I’m Matt Ryall, leader for the Jira Ops product team at Atlassian. Since this is a brand new product, we’ll be delivering improvements quickly and sharing updates...
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