We're trying to use a workflow as suggested by one user in this website:
"(...) I created a Scrum board for the backlog. Our daily Kanban board excludes the backlog status which keeps the team focused on WIP. "
What I would like is that every new issue is created with the backlog status, and when it's moved to a sprint, it's changed to an OPEN status. There doesn't seem to be any workflow in the marketplace that has this functionality though.
When a backlog issue is moved to a sprint, it does appear in the to do column, but it's status remains as "backlog". Since I would like it to show up in Kanban boards as soon as it is on a sprint, this is of no use to me.
>What I would like is that every new issue is created with the backlog status,
Change the "create" transition in your workflow so that it lands in the backlog status instead of Open
>and when it's moved to a sprint, it's changed to an OPEN status.
I don't think you're quite seeing how Scrum boards work with sprints. You gather issues together to be worked on in a sprint. When you're ready, you start the sprint. That does NOT change the status of the issues, it just says "these are the ones you need to work on during this sprint". They're still in whatever status (possibly many) that mean they fall into the backlog, you don't change their status until you actually start to work on them as part of the sprint.
Thanks for the explanation, Nic.
This is basically what I'm doing now. Would you mind checking my workflow here and giving me your opinion?
I agree that this default workflow is painfull.
when you are ready you start the sprint
By starting the sprint, I would see this as equivalent to moving all these tasks to OPEN.
As this is not how it works, what is the point of the OPEN status? You could pick up from BACKLOG and move to IN PROGRESS, skipping OPEN. I am in the process of trying this step to remove the OPEN status from the default workflow.
Starting a sprint means "we commit to doing the things in the to-do list in this sprint". You don't need, or even want to change the status.
Imagine you have a "to do" list of 100 items.
You say "Right, I am going to do these six this week".
What has changed about the way you describe them? They're still "to do". It's not a status change, it's a promise to try to do them. What happens if you don't even look at item 4? It's still "to do" whatever the reason you never got to it.
Oh, and you're questioning a 4 year old question, and looking at the default workflow, which was better than most of the rubbish that was around at the time, but has, of course, moved on.
And, finally, yes, you absolutely should move to a better workflow that matches your desired process.
I'm trying to understand this better and it's giving me a headache.
I discovered that if I add backlog to a column in any of my Kanban boards, it then will show up in the board as long as that issue is on a sprint.
But I don't understand why it should remain on the backlog status when on a sprint :S Shouldn't the expected behavior be to change to some other status, like open?
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