Introduce a Kanban-friendly view of tasks Hot

by David J. Easter on March 20, 2015

Kanban is a popular method for identifying the status and priority of work items.  Typically, a visual "wall" displays the items in columns depending on whether they are "to be done", "in progress" or "completed".  As an item changes status, it moves between the columns, enabling a viewer to quickly see not only the status of an individual item, but the overall progress of a project.  This idea would be to create a Kanban friendly interface within SBM that enables users to represent tasks as cards on a wall within columns to indicate priority and status.

  • At a basic level, a Kanban wall looks something like this:

    A Kanban board showing three columns with

    This idea woudl be to emulate such a card wall within SBM as a view.  The view would be populated by the items in a project and the placement of the items on the wall would be goverened by their status (i.e. which column to be in) or their priority (i.e. how high up the column the item is shown).  The items can either be updated by clicking on them to "drill down" into a typical update form or by just moving/sliding them between columns which will transition the status of the item - e.g. from "To Be Done" to "Doing".  If additional information is required to move an item (e.g. the item must be assigned to be moved to "Doing"), such information will either be requested or filled in through automated rules (e.g. the person sliding from "To Be Done" to "Doing" would automatically become the owner).  Colors can also be used to supplement the interpretation of status (e.g. an item in critical status may have a red outline around it).  

     

    Ideas

    Status
    Target Release
    SBM 11.1
  • Please login to view any attachments.

  • Already have an account? or Create an account
    We will put this idea Under Consideration for the 1H'CY16 release of SBM.
    David J. Easter Commented by David J. Easter August 07, 2015
    #1 Reviewer  -  

    We will put this idea Under Consideration for the 1H'CY16 release of SBM.

    Agreed this would be useful. I would suggest taking this a step further than simply adding "Kanban-like" functionality. In the past, various customers and Serena folks have created Kanban-like report templates, and typically use combinations of custom JavaScript/jQuery and AppScript to change the states of records as they are dragged and dropped. It's a bit clunky considering that SBM applications are intended to follow a workflow, and not potentially jump from state to state.

    What you might consider doing to support this is to make it a separate process app type. Today when I click "New" in Composer I get "Application Process App", "Orchestration Process App", and "Empty Process App". I think you could add a fourth "Kanban Process App" that doesn't leverage transitions or "workflows". Just a collection of swimlanes or states with WIP/Work-in-progress limits, etc.

    I think Kanban support would be a huge benefit for SBM, but would advocate for a clean approach rather than attempting to force Kanban boards on an SBM workflow model. Seems like a square-peg/round-hole issue.

    My .02.
    Steve  LeWarne Commented by Steve LeWarne March 24, 2015
    Top 500 Reviewer  -  

    Agreed this would be useful. I would suggest taking this a step further than simply adding "Kanban-like" functionality. In the past, various customers and Serena folks have created Kanban-like report templates, and typically use combinations of custom JavaScript/jQuery and AppScript to change the states of records as they are dragged and dropped. It's a bit clunky considering that SBM applications are intended to follow a workflow, and not potentially jump from state to state.

    What you might consider doing to support this is to make it a separate process app type. Today when I click "New" in Composer I get "Application Process App", "Orchestration Process App", and "Empty Process App". I think you could add a fourth "Kanban Process App" that doesn't leverage transitions or "workflows". Just a collection of swimlanes or states with WIP/Work-in-progress limits, etc.

    I think Kanban support would be a huge benefit for SBM, but would advocate for a clean approach rather than attempting to force Kanban boards on an SBM workflow model. Seems like a square-peg/round-hole issue.

    My .02.

    I think this is a great idea.
    Fernando Cremer Commented by Fernando Cremer March 24, 2015
    Top 100 Reviewer  -  

    I think this is a great idea.

     

PrintEmail

Recent Tweets