For my project, I would like to use Kanban to track product/feature progress at a high level view, and use scrum to plan out the iterations for each team member.
For example, let's say we have an art asset, on the product view (kanban board), needs to go from concept -> art -> integration -> done. In the scrum board, I would like to do detailed planning on who is doing which part and in what iteration.
My question is:
You've got a few ways to handle this, I'm not sure how you landed on a two-board answer.
It sounds to me like your "Features" are simply Epics. You break them down into Stories for scrum (i.e. "Create concept for feature X" is a story. You could also think about having different types of story).
However, you've also described a workflow of concept -> art -> integration -> done. But then suggested "concept" is a story. I think you need to have a think about the overall processes and map them clearly into types of work and the workflows for each type.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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