LeadDev Berlin 2022 Gergely Orosz

Understand your team's needs and practices before measuring developer productivity. Focus on eliminating friction, prioritizing autonomy and goals, and iterating towards improvement for a more productive team.

Key takeaways
  • Don’t focus on measuring developer productivity without understanding what it means to your team.
  • Developer productivity is not just about technical solutions, but about understanding your team’s needs and practices.
  • Measuring developer productivity can be misleading and requires qualitative feedback from the team.
  • Focus on eliminating friction, distractions, and interruptions to improve developer productivity.
  • Prioritize autonomy, clear goals, and strategic direction to increase developer productivity.
  • Pair programming and code reviews can be effective in improving developer productivity.
  • Don’t rely on vendor solutions that promise to improve developer productivity without understanding your team’s needs.
  • Focus on iterative improvement, taking small steps to make changes and gather feedback.
  • Healthy teams and good practices are essential for improving developer productivity.
  • Autonomy, clear goals, and strategic direction are key to increasing developer productivity.
  • Eliminate unnecessary work and focus on high-impact tasks.
  • Don’t try to measure what you can’t control, such as whether your team is happy or not.
  • Iterative improvement is key to making progress and increasing developer productivity.