[1/2] Developer Joy – How great teams get s% t done - Sven Peters - NDC Porto 2023 (Category Management)

[1/2] Developer Joy – How great teams get s%*t done - Sven Peters - NDC Porto 2023 (Rubric #Management)

Interesting. speech from Sven Peters Developer productivity, developer experience and developer joy:) The author begins by going back in time and recalls Taylor and his scientific approach to factory management. True, the same type of work on the conveyor was carried out there, but by measuring the time of performing various activities, Taylor was able to optimize tools, rest time and other things to increase the efficiency of the plant at times. But now in the information age, many people want to learn how to improve the efficiency of development, but the development is now quite complex and the software development engineer must be able to work on quality, work in the cloud, deploit and pay for their solution. (you build it, you run it). I talked about the same problem on my podcast.Software development engineers in tech companies" But the author suggests moving away from the term developer productivity to developer joy and understand what makes the work of developers pleasant and productive. Dev quality - quality of code base, architecture, lack of technical debt Dev progress - pace of development and delivery of features Dev value - what benefits do the installed features The author describes examples from different teams Jira team wrote code of conduct to review code The Confluence team who wrote a tool to find unstable (flaking) test The Confluence team wrote a pushing bot participating in the code review - this reduced the average time of a PR review with the code review. 3 days 1.2 day

Next, the author talks about the dependencies between the teams that slow down the development. He does this by exemplifying how different interchanges on roads affect highway capacity. When we do normal interchanges that allow cars to stay out of each other's way, we get maximum traffic flow. This author justifies the desire for autonomous teams. And then he talks about the team Trello, where 1 The engineer has to 30 software development engineer. As a result, sde itself takes over most of the standard functions of qa engineers, and therefore do not wait for qa engineers to test their features. Plus, the author talks about the approach with blitz testing, when the whole team tests a critical function. Interestingly, the remaining qa engineers are responsible for qa tuning, test data, databases, and so on.

Developers need to understand dev value. Engineers. (sde) Product managers must work together on the same business. Engineers. (sde) Must be involved in the creation process and understand the problem to be solved It is worth using demos that are important to all teams, they help to see the result and the value they create for customers.

Next, we are talking about measuring productivity and improving indicators Taylor talked about the importance of measuring productivity. If you don’t have anything, start with the DORA metrics. Next, start using your own tool to track progress. In the past, offices used to have wall panels and TVs where you could see the state of the assembly and tests. Checks are now being used to help identify problems and improve performance.

The author recommends using task markup and assessing the time the team spends.

• To change business.
• Keep the lights on. (maintenance) Maintaining development efficiency and improving developer productivity