> Unfortunately, this is only half the story
I'd go further - I'd say in many, many teams, quant KPIs like burndown rate and velocity are downright misleading and often harmful. It provides the wrong incentives for the team - it stresses output over outcomes. The main thing that should matter is how quickly you're improving things for your users - their metrics are the ones to track.
I'm a bit biased as I'm working on a startup [0] that is trying to click with teams that really value collaborating closely to provide impact for their users over being a feature factory that maximizes their velocity.
0: https://kitemaker.co - the product management and collaboration tool that's crazy fast and has deep integrations to your favorite tools like GitHub, Figma, Slack and Discord.