I suggest you ...

add the optional ability to post backlog in a column on the visible board view

On a physical kanban board, you can have an area to "display" the backlog along with the WIP which gives upstream and downstream stakeholders the ability to look into your backlog and see what you (or the operational review board) did not select for prioritizing. This is very often useful when not everyone who has a stake in your work can attend every prioritization meeting and you have a relatively high velocity and variable WIP flow.

10 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    James Common shared this idea  ·   ·  Admin →

    2 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Michael F Forni commented  · 

        Hello. I recently joined this community.
        Won't waste time in addressing further compliments to a Team that did such a marvellous job.(They KNOW they delivered GREAT value, indeed!) but more effectively sharing a possible upgrade.

        I definitely agree with James.
        The Backlog (I know this is Kanban, not Scrum so I'm not even mentioning the Sprint Backlo ;) ) should be always visible (Transparency) though manageable by the PO only.
        Whatsmore it should be visible in the App version, too (or it's me that I can't find it)

        Obviously it should be a "tickable" option in the setup, so Teams that think they don't need it visible (even temporary), could make it invisible, giving more space on the screen to th eKanban board.

        Cheers,
        Michael

      • Bors Vesterby commented  · 

        This is critical for Lean project work where the goal is to visualize all work including intake into your backlog. Hiding the backlog, frankly, goes against a fundamental tenant of Kanban which is to make ALL work visible.

      Feedback and Knowledge Base