Kanban board

Rubén Álvarez

Smartsheet is a very powerful tool that, with some changes, could be easily applied in agile team environments and thus compete more effectively with Jira or Azure Boards.
Features:
- Rename “lane” to “column,” as this concept is incorrect from the perspective of a Kanban board and how it is understood in this context.
- Add support for lanes (horizontal rows).
- Add support for WIP limits (maximum cards allowed per column or lane); for now, columns are sufficient.
- Introduce the concept of subcolumns. A column represents a state, such as “Build,” which in turn would require substates like “Doing” and “Done” (each should have its own subcolumn).
- These subcolumns should be measurable to retrieve some Kanban metrics, such as Flow Efficiency, which measures the time a card spends in “Doing” versus the total time.
- Each substate should include a description or something similar to define explicit policies that indicate when a card can move to the next column (and make this accessible on the board).

With these changes, Smartsheet could even compete with tools like SwiftKanban.

Georgie

Thank you for providing your feedback! However, since there are 6 separate requests in the same post, I've removed this post from the Product Ideas section - each individual idea needs to be its own separate post so that other members can vote on which one they agree with, and so that the Product team can post updates for each item as they likely won't all be addressed at once.

I found a similar idea post for your suggestion of horizontal rows in card view here:

• Custom Visualizations in Card View: horizontal rows & swim lanes

Please add your vote to the above idea if it matches your request and if not, please create a new idea post with your suggestion.

 Additionally, create a separate unique post for each of your other separate ideas (listed below) so that other members can vote on the ones they want to see Smartsheet implement as well:

• Rename “lane” to “column” in card/board view
• Add support for WIP limits in card/board view (maximum cards allowed per column or lane) 
• Introduce the concept of subcolumns in card/board view. A column represents a state, such as “Build,” which in turn would require substates like “Doing” and “Done” (each should have its own subcolumn).
• These subcolumns should be measurable to retrieve some Kanban metrics, such as Flow Efficiency, which measures the time a card spends in “Doing” versus the total time.
• Each substate should include a description or something similar to define explicit policies that indicate when a card can move to the next column (and make this accessible on the board).

Thanks,

Georgie

Rubén Álvarez

Hi.

I created these proposals:

• Rename “lane” to “column” in card/board view
• Add support for WIP limits in card/board view (maximum cards allowed per column or lane)
• Introduce the concept of subcolumns in card/board view "Doing / Done"
• Include a description in each stated for a Board View

Thanks