Flow framework was used for an eBay Velocity Initiative program to help the ideation <-> ticketing side of velocity value stream.
The metrics we’re using weren’t super clear to me. Here are the definitions of things in my own words:
flow efficiency: active time vs total time (e.g. how long is it waiting) flow time: how long does it take to close an issue over time period (started -> closed) flow velocity: closed issues over the time period flow load: number of unclosed issues (total work liability)
In general, it seems like we want to have:
- just in time work creation
- lean backlogs
- quickly doing the work that we have to do