Recently we setup multiple Kanban boards to help with our agile project however we have realised that we will always have stories that run over our sprint periods of 2 weeks. I was hoping someone had examples of how to handle this or how we can better handle this.
Our setup is as follows:
- Agile board for the project and this essentially tracks the status of stories with: To Do, In Progress, Done & Closed
- Kanban board for artists which has: To Do, Concept, Model, Texture, Rig, Animate, Review, Approved. Once things are approved it moves to Done in the Agile board.
We have other boards but for the purpose of this question the below is enough detail I believe.
Then we have stories which for example are "Character #1" and we estimate a total time to complete this of say 13 days. We use points but over time we have realised our perception of hours and points are very similar.
The main thing to note is that the 13 days is made up of say: 1 day concept, 3 days model, 3 days texture, 2 days rig, 4 days animate.
If we now have the single story Character #1 then when we add it into the sprint (which is 2 weeks) then this will run over. Obviously this is against the concept of agile.
Prior to setting up the kanban boards we would rather have an Epic of Character #1, which had stories for concept, model, texture, rig, animate and each had their days. This was a lot easier to plan a sprint as it means we could correctly allocate the right amount of work. The downside was that we didn't follow a clear path through a workflow as per the kanban boards.
Does anyone have any good workflows/suggestions that would work well in this instance?
