How to Improve Developer Productivity • Jez Humble • YOW! 2020

Good. speech Jez Humble at the Yow conference, where he spoke briefly about the productivity of development. Jez is the co-author of Accelerate, and this talk looks like a brief sammari of an influential book I’ve covered in my posts before. 1, 2, 3. It starts with poor productivity metrics: Lines of code - once it was a popular measure, but now everyone understands that less is better. velocity is a relative measure of team level that cannot be used to compare commands with each other and can be easily manipulated if desired.

• utilization - if you chase recycling, then we face Little's law and get into a situation where the next task can be approximately infinity in the queue. And then Jez goes on to the story, and what do we pay attention to, and what we get is that productivity is the story. Team metric: Teams bring results, not people System-level outcomes – look at system results, not local outcomes Outcomes, Not Output – Maximize results, not the number of tasks done And then they come on stage. DORA metrics divided into two categories n Software delivery performance tempo includes delivery lead time and deployment frequency Software Stability: Mean time to recover and change fail rate And Jez sorts them out in detail. Jez talks about culture and remembers it.
• Westrum's research, about which I have already wrote. There were three types of cultures: pathological. (pathological)bureaucratic (bureaucratic)productive (generative) Aristotle research conducted by Google for its teams. What makes a team effective at Google? Top-1 Psychological safety is a factor. I already am. told about this study.

#Management #Engineering #Software #SoftwareDevelopment #SRE #Devops #Leadership #Processes #PlatformEngineering