Kanban Teams often work on Task level workitems. Sometimes the Workitem in the Kanban board is really a Task, which has a detailed hourly estimate, ToDo hours, and tracked Done hours.

Agility does have the not concept of Task level Kanban items. The Story is the primary workitem on a Kanban board. So in order to track a small Story on a Kanban board you have to create a Task under it, then the two workitems are kept separated by the user interface (Storyboard ot Taskboard).

The Task board shows a Story Card and a Task card. The Story board only shows the Story card. You could keep the concept of the Storyboard, but enhance the visualization by allowing the parent child relationship for Tasks. This would be visually similar to what you do on the Roadmap Timeline view with Epics showing a + Plus icon indicating there are Features under it.

In summary, Kanban workitems are often small Task level items. We can keep the tool's Story/Task relationship but improve visually and functionally how a Storyboard supports Kanban by pairing the Story/Task cards so those simple Kanban workitems are better integrated and tracked.

by: Steven C. | about a month ago | User Interface