Kanban: How to manage features that are developed in several pieces?


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?


1 answer

1 accepted

0 votes
Accepted answer

How about creating three sub-tasks for your feature? This way you cannot release your parent feature until all three sub-tasks are completed.


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?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,364 views 15 19
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you