Most developers seem to be unaware of the SEI's Personal Software Process (PSP) (https://en.wikipedia.org/wiki/Personal_software_process https://en.wikipedia.or

Most developers seem to be unaware of the SEI's Personal Software Process (PSP) (https://en.wikipedia.org/wiki/Personal_software_process https://en.wikipedia.org/wiki/Personal_software_process). Abstract: The Personal Software Process (PSP) is a structured software development process that is designed to help software engineers better understand and improve their performance by bringing discipline to the way they develop software and tracking their predicted and actual development of the code. It clearly shows developers how to manage the quality of their products, how to make a sound plan, and how to make commitments. It also offers them the data to justify their plans. They can evaluate their work and suggest improvement direction by analyzing and reviewing development time, defects, and size data. There is also a corresponding Team Software Process (https://en.wikipedia.org/wiki/Team_software_process https://en.wikipedia.org/wiki/Team_software_process). Instead of coming up with more ad-hoc methods of measuring "Developer Productivity" i think it would be better if people build upon this. It is a framework to define a specific tuning process and hence easily adapted to any methodology (Agile or otherwise). The reason i like the PSP/TSP is that it is solely for the Developer's benefit (no Management need be involved) where i the Developer measure my performance on various metrics (which i can define) and improve them as i need to i.e. it is a proper Self-Feedback loop.