Hello ... we're trying to use Jira Kanban board in an iterative process for capturing, managing and working on individual change requests and small projects (broken into sprints). We have multiple developers who may work across multiple applications/systems, either on individual changes or groups of changes (sprint). Different team members can each be working on different apps/systems.
We are capturing all demand items onto the backlog. One of our contentious aspects between IT team and the business is when to move items from backlog to todo.
The business/stakeholders would have IT move items to todo asap, of course. They want their requests to get soonest to developers. A minimum is that the backlog item must have clear requirement and estimate before it could be considered movable to the todo list.
Developers/IT planners on the other hand don't want to create a huge TODO list so as to prevent items getting old and/or becoming outdated before they get dragged into the in-progress status.
What are some strategies your all using for when to keep items on Backlog (OPEN status) and/or when to move them to the TODO (ACCEPT status) list?
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
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