Flow provides metrics useful for large distributed engineering organizations that both apply to individual achievement and team collaboration. It offers fundamental metrics such as coding days, impact, and time to merge that teams need to be able to improve. The investment categories report is very useful for reporting on where the team is actually spending their time, and DORA metrics can help accelerate time to shipping code. Unlike a lot of tools like this Flow offers hierarchical team structures that are useful for large groups. Review collected by and hosted on G2.com.
Flow integrates tightly with Git, and is dependent on the flow teams use to be able to capture some information. For example, if individuals do most of their work in private forks, and then squash and merge their changes, some data is lost and certain metrics will not be accurate without a larger administrative overhead, such as setting up multiple Github connections to read individuals' private spaces. Related to this there are issues around merging identities to make sure work is attributed to the right person that can become a burden at the scale of hundreds of engineers. Review collected by and hosted on G2.com.







