How to Measure Developer Productivity

Track three numbers. Revenue Per Engineer shows whether engineering output translates to business value. Connascence Degree shows whether the system helps or hinders. Coordination Overhead (meeting hours per release) shows how much time goes to talking versus building.

The real productivity killer is context switching and coordination overhead. If your engineers spend 30 percent of their time in meetings, that's an architectural problem, not a people problem. Fix the architecture and productivity follows.

Drop story points entirely. They are subjective, non-convertible, and disconnected from business value. Replace them with time-to-ship and cost-per-feature.