HaystackAnalytics：COVID-19对软件工程师的影响报告_9页_8mb

Summary of the Study on the Impact of COVID-19 on Software Engineers

Core Content

This study aimed to understand the impact of the COVID-19 pandemic on the wellbeing and productivity of Software Engineers in the United Kingdom. Conducted between the 23rd and 24th of June 2021, the research was carried out in partnership with Survation, a reputable research agency known for its accurate predictions in major political events.

The study surveyed 258 Software Engineers aged 18+ and used a rigorous methodology to reduce self-selection bias, including online interviews with Survation's panel members. The results highlight significant challenges in terms of burnout, software reliability concerns, and inefficient development processes.

Main Findings

Role Distribution

• 26% of Software Engineers are solely focused on product development.
• 74% are involved in operations in some capacity.
• 44% are in hybrid roles, combining both product development and operations.

Burnout

• 83% of Software Engineers reported experiencing burnout.
• 55% felt they had "great" or "moderate" levels of burnout.
• 81% reported that the pandemic increased their burnout.
  • 32% felt this was true to a "great" extent.
  • 30% felt this was true to a "moderate" extent.
• 40% cited increased workload as the main reason for pandemic-related burnout.
• In general, the top reasons for burnout were:
  • High workload (47%)
  • Inefficient process (31%)
  • Unclear goals and targets (29%)

Software Reliability and Process

• 83% of Software Engineers expressed concern about software reliability at their workplace.
  • 20% were concerned to a "great" extent.
• 55% of engineers reported frequent delays in delivering work due to inefficient processes.
  • 31% of those experiencing burnout attributed it to "inefficient process."

Cycle Time

• Cycle Time is defined as the time it takes to begin working on a feature and reliably deploy it into production.
• 50% of Software Engineers reported Cycle Times of 1-3 days.
• 59% reported Cycle Times of less than 3 days.
• The study grouped teams into performance categories based on Cycle Time:
  • Elite Performers: 31%
  • High Performers: 47%
  • Medium Performers: 16%
  • Low Performers: 4%
• Cycle Time is a key metric for understanding team productivity and flow alignment, with elite and high performers representing a supermajority.

Key Insights

• Burnout is prevalent among Software Engineers, with high workload being the primary cause.
• The pandemic exacerbated burnout, particularly due to increased workloads.
• Software reliability concerns are widespread, with many engineers expressing worry about the stability of their workplace systems.
• Inefficient processes are a significant contributor to both burnout and delays in delivery.
• Cycle Time has become a critical indicator of team performance and productivity, with a growing number of teams achieving short Cycle Times.
• The study suggests that focusing on flow optimization rather than just the volume of work delivered can lead to better business outcomes and reduced burnout.

Conclusion

The study demonstrates that technology teams are increasingly adopting flow-oriented practices, with a majority of Software Engineers reporting short Cycle Times. However, burnout remains a major issue, driven largely by high workload and inefficient processes. The research emphasizes the need to consider developer wellbeing when evaluating engineering productivity and highlights the importance of metrics like Cycle Time in driving performance improvements.