Better Backlog Management for Scrum project?

Wayde Wyatt

Does anyone have a good way to better manage the backlog workflow for a scrum project?  We took ideas from "Groom You Backlog Like A Boss" 

https://www.atlassian.com/blog/jira-software/groom-backlog-like-boss-jira-software

and at least have separated the backlog into "Bugs", "Technical Debt", "Backlog".  However, these are for issues that have already been triaged, vetted and approved for development. 

What we're looking for is some way to move backlog issues through swim lanes like "Triage", "On Hold", "Actionable", etc.  This would help us ensure that the only issues on the sprint backlog are those that are ready for development.  We thought about creating a separate "Backlog" Kanban project and then periodically moving "Actionable" issues to the sprint project?  The downside of this is that the issue number would change causing  a break for anyone wanting to check on the status of the original request.

Any ideas?

Karri Adkins

I have had to add a precursor set of status steps in my workflow to account for things like this.  All my workflows, no matter what project instance they are under, include a triage workflow.  Once they pass through those steps it goes into the backlog for the engineering team.  So in essence, there are two self contained workflows.  When the ticket is created it starts in the triage workflow, when triage is complete, they push it to the backlog.  Not sure if this makes sense, but it has made a world of difference for us.