Skip to main content

Kanban metrics

We are prioritizing from this pool of metrics:

  • Througput per board

  • Cycle time per board or single item.

  • When it will be done, based on throughput and cycle time. Item level.

Status: Completed11 comments

Log in to comment and vote

Comments11

  • Vidas changed status to Completed
    Team•

    Nov 20, 2023

  • Vidas

    Team•

    Nov 20, 2023

    We've completed first batch of metrics as PoC through layers. After we gather data we will run the second iteration which is metrics per column (or similar alternative).

  • Vidas changed status to In Progress
    Team•

    Aug 16, 2023

  • Vidas changed status to Planned
    Team•

    Aug 6, 2023

  • Tom Davidson

    •

    May 18, 2023

    when as in a Monte Carlo fed histogram?

    • Vidas

      Team•

      May 18, 2023

      Tom Davidson: Monte Carlo is one of the possible techniques to solve "when" question. But I cannot confirm that it will be the one chosen, we are investigating proprietary math/statistical solutions as well.

    • Tom Davidson

      •

      May 18, 2023

      Vidas: thanks, my orgs will not be interested in proprietary or black box analytics.

      One of the powerful things of kanban is it's timelessness. Flow metrics are not hip and new, but timeless and proven.

      Why do something different?

      Maybe expose a Prometheus endpoint that we could scrape for our own analytics?

    • Vidas

      Team•

      May 19, 2023

      Tom Davidson: very valid point regarding black-box analytics, non-transparent method will be met with skepticism.

      We are not yet committed to any technique. Monte Carlo has it's own flaws by focusing only on throughput and quatifying items as almost equal pieces. We do not intended to invent something out of the blue, we still want to use flow metrics.

      Goal here is to be more accurate and tangible, rarely an average user would get value from Monte Carlo, at least how it is being done nowadays in other Kanban tools. If we fail to find a better way, we go with Monte Carlo

    • Tom Davidson

      •

      May 20, 2023

      Vidas: work items of different sizes do not matter for kanban or flow metrics and if teamhood goes down that path of story points and faux kanban then Im out.

      The predictably of a flow system is all about probabilities which monte carlo is perfect for. 85% confidence based on historical performance that we will hit this milestone by such and such date is immensity more valuable to predictability than sprints, sizing, and deadlines (ie SCUM bull). With kanban and flow metrics we use data instead of human judgment to make forecasts - sizing will do more harm than good because it poisons the forecast with human judgment.

    • Vidas

      Team•

      May 22, 2023

      Tom Davidson: thank you for caring and sharing. I will dedicate time to get wiser before we reach some sort of conclusion. And I will share the idea here prior to even making a comittmet to deliver a specific product change.

    • Vidas

      Team•

      Sep 6, 2023

      We have started with Cycle time and Throughput, we will show these metrics on the board level. Then we will use them for our own concept of layers. Lastly, monte carlo simulation will follow.