There are a number of items on IdeaSpace concerning Kanban. In order to fully support Kanban, these things need to be consolidated into an epic and rolled out as a package.
Here are a few that I consider important. I'm sure that there will be others.
- Swim lanes/service levels/fires, supported by visual cues such as color codes, cycle time easily
- visible on storyboard, etc.
- Show item count in each column next to WIP limit.
- WIP limits across multiple columns.
- Show explicit policies for each column.
- Forecasting tool needs to work when there are no fixed length time boxes. This could be based on cycle time or throughput, or preferably both.
- Better support for Kanban metrics. For example cycle time broken down by service level, ability to drill down into reports to see underlying data, etc.
Kanban is becoming very popular and I think it would be a good idea for VersionOne to fully support this. All that's available now is a storyboard and real Kanban support is fairly superficial.
by: Mike C. | over a year ago | User Interface
Comments
I agree with this comment and hope to see a Kanban release soon. My primary issue with V1/Kanban stems from the fact that we have three development teams, only one of which follows Kanban (other two are scrum). We often have one project that has some work going to a Kanban team and some work going to a scrum team. This is difficult to manage in V1 because a project requires its own iteration schedule. We're having to create two projects just to get the work done. I'd like to see some efficiencies there.
Looking forward to the Kanban release as well. Would also like to see WIP limits by teams or at least have the system determine when a WIP limit is exceeded based on the Storyboard team view and not the number of backlog items in the catagory for the full project. For example, our projects are defined along releas of the product so the norm is that multiple teams will be working on the release (for different functional area) but exceptions to the limit are "calculated" on the project level. For example, if I had a project with two development teams each with two backlog items "In progress" and a project WIP limit of (3) if I showed the story board filtered by each team it would show only two backlog item in the "In progress" state but as the project has four the column display for the team's story board would show that the team has exceed the WIP limit...
Best solution for us would still be team level WIP limits
I would also like to see the option of using WIP limits on the Taskboard. We plan to start up a Kanban Board using V1 and would like to break a Backlog item into tasks that subscribe to our WIP limit policies.
I would add my voice to this as well. I would especially like to see limits segmented by column AND row and by resource as well. There are several serious limitations to using the LKK integration into V1 so this should not be considered as solved by the release of the LKK integration.
A number of aspects of this request have been implemented, so we're closing this one out. As of the Fall '12 release, the original kanban capabilities have evolved to include: swim lanes, coloring options, wip limits across columns and aging alerts. With the addition of Team Rooms, all of these capabilities can now be defined on a team-by-team basis even in cases where the teams are working in the same project level. In addition, Analytics offers the abilities to create custom reports on Epics and details rolled up into them.
Have other needs? Please let us know by creating new ideas for them.