In the past few weeks, we have been working with a group of Tech Leads to help improve team effectiveness. During this process, the question of how to provide feedback on the performance of software developers emerged. Measuring the performance of a developer is not a simple exercise. It cannot be reduced to a simple data point or even several. We looked into an approach that didn't focus so much on individual metrics but rather on trends and a systemic view of performance. The article titled 'The SPACE of Developer Productivity: There's More to it than You Think' inspired us. We identified two essential areas to improve our understanding of software developers' performance:
- Performed Activity (quantity and quality): Here, both the quantity and quality of the developments performed should be analysed. This helps us measure not only productivity but also the effectiveness and efficiency of the developer; do they look for simple solutions?
- Contribution to Team Success: Beyond individual achievements, it is crucial to assess how the developer impacts the collective goals of the team. Collaboration and synergy are vital for joint success.
Various elements can be utilised to evaluate trends and obtain a comprehensive view of performance in these areas:
- Work Items: Monitor the number of tasks or tickets completed by the individual in tools like Jira or Asana, and analyse the complexity of these tasks to better understand their ability to handle technical challenges and deliver effective solutions.
- Collaboration and Communication: Assess their effectiveness in collaboration, communication, and coordination within the team and with other teams. The quality of their comments, their promptness in addressing suggestions, and the fluency in communication are essential for a positive and productive work environment, ensuring everyone is aligned and critical information is effectively shared.
- Business/Development Balance: Evaluate proactive reduction of technical debt and meeting deadlines to balance the needs of the business with those of development.
- Unit Tests: The quality of unit tests is a direct reflection of attention to detail and commitment to software robustness.
- Pull Requests and Commits: Measure the number of commits made and pull requests opened and closed by the individual. The quality and frequency of these contributions indicate the developer's consistency and impact on the project.
- Code Reviews: Quantify the code reviews conducted by the individual, both in terms of initiation and participation, demonstrating a commitment to continuous improvement and the quality of both individual and collective code.
- Generated and Resolved Bugs: The severity and number of errors generated and resolved provide a clear view of the developer's ability to maintain and improve software quality.
- Incident Mitigation: Proactivity and ability to handle critical situations and create temporary solutions reflect the capacity to solve problems under pressure.
- Design Documents and Specifications: Count the design documents created or significantly contributed to, evaluating their quality to ensure the software is well-planned and aligned with requirements.
- Builds: Count the times the individual’s code has compiled without errors. The ability to upload code that passes compilations without errors is a key indicator of the quality and reliability of their work.
- Improvement of Tools and Processes: Participating and taking responsibility in the continuous improvement of tools and processes demonstrates a commitment to efficiency and excellence.
- Infrastructure Use: Efficient management of development resources, such as test servers, is crucial to maintaining a productive workflow.
Finally, it is also crucial to evaluate how aligned the Software developer is with the organisation’s values. For example, if respect is a fundamental value, it is important to observe the behaviours they exhibit in relation to this cultural value. Measuring the performance of a developer is not simple exercise and needs a holistic view. These suggestions are to help with regular feedback and not once a year performance review. Most developers crave useful feedback to help them grow and understand if they are doing a good job. Hopefully the points above can help the developers and their tech leads / engineering managers have better conversations around their performance.
#developerproductivity #techlead #engineeringmanager #performancefeedback
