Measuring developer productivity is like observing quantum state, the act of measuring it generally fucks it all up. Rather than task the developers with all m

Measuring developer productivity is like observing quantum state, the act of measuring it generally fucks it all up. Rather than task the developers with all manner of bureaucratic Agile bullshit like tracking hours, arguing about story points, submitting to kindergarten-style daily stand-ups, velocity tracking, retros, etc; I would suggest a different tact. How about measuring developer productivity by observing if they're building what you need at the rate you need it built. If not, then you need to figure out if you can afford to replace them with someone that can.