I'm trying to move my team from Scrum to Kanban.
Say I have a feature than can be developed and tested in three independent chunks, but the feature isn't complete until all chunks are complete.
What's a good approach to prevent us from releasing parts 1 and 2 while part 3 is still in development?
It feels like an Epic should be employed but how do I manage the workflow of the epic?
You're probably correct. I've steered clear of sub-tasks in the past because they seemed to add to the overhead, but I should probably revisit this.
Would the sub-tasks move through the Kanban board independently? E.G. Could one be assigned to dev A, one to dev B and one to a QA person? Or are they all "in development" until everything is complete?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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