Ask HN: KPIs for a Development Team?
Cycle time is a hugely useful metric - how long does it take the team to go from idea to the user being able to actively use your change.<p>This can  be bracketed if needed - if you have issues with product you can just take it from the time the team pick the work up to when it it delivered. If you are bound by a release cycle - then you can just take it until the code is packaged up ready to release - but both of those brackets hide inefficient parts of the flow.<p>I&#x27;d steer away from developer commits etc - and look more at other measures of quality - how many bugs do you have (live bugs) in your various priority types an how long is their average age.<p>Some starters for ten.