Facing a kanban board workflow issue and don't think we've quite nailed a solution yet.
We're building an app backed by a middleware tier serving up JSON content. Nothing new about it.
Issue we have is maintaining a solid workflow.
At the moment we have the following (of relevance) columns: Ready 4 Dev | In Dev | Ready 4 Test | In Test
We ALSO have horizontal swimlanes for iOS | Android | Server cutting across each of those columns.
We ALSO have colour coded tickets (red = bug, purple = server etc).
Ideally, in a sequential world, we'd have columns for f/e and b/e, but needless to say, work can happen on components in parallel.
Several ideas we've had:
Use ONE ticket/card/story that sits in an "in flight" lane while it's composite tasks flow across. It's only completed once all tasks have completed
A STORE is broken down into TWO (or maybe more) tickets (basically tasks) abut we remove the horizontal component (b/e and f/e) swimlanes
Feature: T&Cs (as part of an MVP)
Ticket 1: Format and style HTML docs Ticket 2: Upload HTML docs to server and provide addresses Ticket 3: Implement WebKit calls to HTML files Ticket 4: Middleware service to communicate between client and DB (to record when and what version T&Cs were agreed to on registration)
So there are many related tickets floating above that each need different people or teams working on them to complete a somewhat trivial feature.