Several people are always adding to the backlog and this is becoming a problem when the backlog is already in a priority order. As new issues are added, then the backlog will get mixed up and it is impossible to track what was where before the new items were added.
Can we force when a new item is added to always go to the bottom of a scrum backlog on the planning board?
I know the workaround is that you need to select the existing bottom issue on the backlog, then create a new issue, to ensure the new issue gets added to the bottom. But this is not a fail-safe solution and our backlogs are becoming unmanageable.
Thanks in advance
I am pretty sure the default behavior is that a new item gets added to the bottom of the backlog. Is it not like that for you?
Correction: Since GreenHopper 6.1.2, a new feature was added so that newly created items immediately below the currently selected item. Honestly I prefer the old way where everything is added to the bottom by default.
retrain the users not to use the Create button (which does insert below the currently-selected backlog item)
Instead, teach them go scroll to the bottom of the backlog (or future sprint) and click the "+ Create Issue" grey text (this is in both JIRA 6 and JIRA 7).
I prefer this way of working because "product backlog items are placeholders for a conversation" and when you type and tap return, all the user is doing is populating the Summary field.
The Product Backlog contains two queues: coarse and fine, or not-yet-refined and refined (done using Backlog Refinement). So simply entering a single line is following method: it's a placeholder for a conversation, and you'd flesh it out later. Also, they can always go into the item and add details anyway (but agility/lean does require Just In Time analysis so the Agile Coach should be ready to spot this and encourage them not to do this just yet: use retrospectives to flesh out this part of the process as required, but initially just implement a minimum viable way of working: Agile Principle #10 states that "Simplicity ... is essential" - the more full text is "Simplicity - the art of maximizing work not done - is essential".
in Summary: don't use the Create button: it's way too tempting to populate all those fields (that I bet the JIRA Admin hasn't yet gotten around to redesigning the Create Issue Operation Screen ; just as I bet all those superfluous out-of-the-box IssueTypes haven't been rationalized either... )
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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