2024年开发者体验报告：揭秘影响开发团队效率的关键因素.pdf

State of developer experience report 2024Get a fresh look at whats getting in the way of developer satisfaction and productivity in the age of AI.STATE OF DEVELOPER EXPERIENCE REPORT 2024B1 A note from Atlassians CTO3 Where we sourced our data4 PART 1 The state of developer experience in 20244 Developer productivity isnt well understood or enabled7 Experience and productivity are seen as being closely intertwined9 Interest in developer experience is growing,but efforts are lagging12 PART 2 How can we improve developer experience in 2024 and beyond?12 The building blocks of a great developer experience15 Measuring developer experience16 Key performance indicators(KPIs)18 Atlassians“developer joy”initiative20 PART 3 Additional resourcesTable of contentsSTATE OF DEVELOPER EXPERIENCE REPORT 20241A note from Atlassians CTOSoftware development teams are dealing with more complexity than ever.Theyve moved from monoliths to microservices,seen an explosion in APIs,started to explore generative AI tools,and often work in a distributed environment.Developers are being asked to manage everything from security vulnerabilities to cloud configuration,which leaves little time for writing code.None of this is surprising,given the recent spate of layoffs in the tech sector and tighter purse strings across the board.Teams are being asked to do more with less.Maximizing productivity is the order of the day.The trouble is that knowledge worker productivity is notoriously difficult to quantifyand as the saying goes,you cant improve what you cant measure.Meanwhile,theres a significant body of research showing that happy workers are productive workers.So instead of worrying about what makes developers more efficient,what if we think about what makes them happy?Not the surface-level happiness you can buy with high-dollar swag and on-tap kombucha,but the deep sense of fulfillment that comes from creating something great.RAJEEV RAJAN Chief Technology Officer at AtlassianSTATE OF DEVELOPER EXPERIENCE REPORT 20242Atlassian engineering is betting big on the idea that carrots are more effective than sticks.If we make developers jobs more satisfying,we believe productivity will improve organically.Thats why we embarked on this research.We surveyed 2,100+developers and managers across a range of industries to get a fresh look at what keeps work flowing smoothly vs.what introduces friction,and how they feel about their work environments in the age of microservices and AI.While this aggregated picture wont perfectly reflect your teams situation,it should provide some useful clues.That said,reporting problems without offering solutions isnt the Atlassian way.So we also partnered with DX,the engineering intelligence platform designed by leading researchers.By incorporating their existing work with this new data,we were able to include a section at the end with specific recommendations for engineering leaders.If you want to learn more about the challenges to developer experience,see Part 1 on page 4 If you want to improve the developer experience at your organization,see Part 2 on page 13 If youre looking for more resources on developer experience,see Part 3 on page 20Speaking candidly,developer experience is an ongoing challenge for Atlassian,too.This research uncovered new information that my team and I are figuring out how to act on.We dont have all the answers,but we do have a mission to unleash the potential of every teamstarting with our own.As we continue our developer experience journey,well keep sharing what we learn along the way.I hope the information in this report will spark ideas for experimentation and investigation as you seek to unleash your teams potential.RAJEEV RAJAN Chief Technology Officer at AtlassianSTATE OF DEVELOPER EXPERIENCE REPORT 20243Where we sourced our dataIn February 2024,we worked with Wakefield Research and DX,an engineering intelligence platform,to learn more about:1.The state of the developer experience at global organizations2.Progress and limitations to developer experience improvements3.The future of developer experience,including the impact of AITo understand the perspectives of both engineering leaders and developers,we ran two global surveys:Wakefield Research surveyed 1,250 engineering leaders in the US,Germany,France,and Australia.DX surveyed 900 developers around the world,including the US,Germany,France,and Australia.*DX also surveyed developers in the UK,Sweden,Lithuania,Estonia,Spain,Ireland,Ukraine,Denmark,Switzerland,the Czech Republic,Canada,Brazil,and India.Developers and leaders know developer experience is critical to attracting and retaining talent.But that doesnt mean leaders and developers are always on the same page.There are mismatches between leader attitudes and what developers actually experience.Less than half of developers think their organization prioritizes developer experience.86%of leaders believe attracting and retaining the best developer talent will be almost impossible without improving developer experience.41%of leaders use tools that measure productivity to assess team satisfaction.Leaders believe AI is the most effective way to improve productivity and satisfaction.Developer experience is important or very important for 63%of developers when deciding whether to stay in their current job.2 out of 3 developers are still losing 8+hours a week to inefficiencies in their roles.But 2 out of 3 developers arent seeing significant productivity gains from using AI tools yet.Developer experience in 2024:the highlightsSTATE OF DEVELOPER EXPERIENCE REPORT 20244PART 1The state of developer experience in 2024Developer experience n.dih-vel-uh-per ik-speer-ee-uhnsDeveloper experience focuses on the lived experience of developers and the points of friction they encounter in their everyday work.Developer productivity isnt well understoodor enabled44%of developers lose 8 hours or more of their working week to inefficiencies.Less than half of developers believe leaders are aware of these issues.The last few years may have seen a lot of interest in developer productivity,but that doesnt mean organizations are enabling their developers to be as productive as possible.In our survey,69%of developers say theyre losing 8 hours or more a week to inefficiencies in their role.How many working hours a week do developers lose to inefficiencies?0 hours:3%4 hours:28%8 hours:36%12 hours:22%16 hours or more:11%69%STATE OF DEVELOPER EXPERIENCE REPORT 20245Hiring top talent only to have them blocked by organizational impediments is pointlessand expensive.For an organization with 500 developers,losing 8 hours per week costs roughly$6.9 million over the course of a year1.With such significant losses on the line,its essential to understand the main friction points in the daily lives of software developers.Our study found that the top contributors are technical debt,along with a lack of documentation,processes,focus time,and direction.*According to Stack Overflows 2023 Developer Survey,the average salary for developers worldwide in 2023 was$69,767.If a developer loses 8 hours weekly on average to inefficiencies,those inefficiencies come at an annual cost of$13,954.40 per engineer per year.The larger the organization,the higher the cost of inefficiency.While just under half the developers we surveyed(44%)believe that leaders at their organization are aware of these issues,we found that almost all leaders(99%)do acknowledge that the developer role has become more complex.According to these leaders,these complexities are primarily seen as being driven by understaffing,technology,and tooling.Top 5 areas of developer time loss according to developers*multiple choice questionTop 5 areas of developer role complexity according to leaders*Tech debt(59%)Insufficient documentation(41%)Build processes(27%)Lack of time for deep work(27%)Lack of clear direction(25%)0 10 20 30 40 50 60%Understaffing(48%)Expansion of the developer role(47%)New technology(47%)Switching context between tools(43%)Collaboration with other teams(43%)0 10 20 30 40 50%*multiple choice questionSTATE OF DEVELOPER EXPERIENCE REPORT 20246The problem with productivity metricsMost leaders admit the metrics they track are ineffective for measuring developer productivity.Our survey of engineering leaders shows the most commonly used metrics are the amount of code written,the number of story points completed,and hours worked.We also found that leaders arent exactly enthusiastic about them.For example,more than half of the engineering leaders using these metrics find them ineffective as a measure of developer productivity.Measuring hours worked is particularly problematic since it only shows how long a developer spends on their laptop.As weve seen,that time doesnt all go into coding.In fact,69%of developers lose 20%or more of their time to inefficiencies at work.This might explain why 55%of leaders who use“hours worked”find it ineffective.Top 5 ways organizations are measuring productivity and how effective these measurements are*multiple choice questionAmount of codeUse and find effectiveUse and find ineffectiveDont useDeployment frequencyStory points per sprintHours workedChange failure rate0 20 40 60 80 100%69%of organizations measure developer productivity by hours worked.of developers are losing 20%or more of their time to inefficiencies at work.38%STATE OF DEVELOPER EXPERIENCE REPORT 20247Experience and productivity are seen as being closely intertwinedWhile some organizations seem to recognize developer experience as a distinct concept,many others appear to conflate developer productivity and experience.For example,41%of respondents said their team uses the same tool to assess developer productivity and experience.Our survey didnt provide visibility into exactly which tools are running double-duty on productivity and satisfaction assessment,or exactly which metrics are being pulled.But it does present a red flag about making sure youre tracking the right metrics using the right tools.Top methods leaders use to assess developer satisfaction*Generic employee surveys(51%)A developer experience platform(43%)Developer-initiated meetings with managers(41%)Developer productivity tools(41%)0 10 20 30 40 50 60%*multiple choice questionThe survey also revealed engineering leaders are looking at a mix of automation,tooling,and culture and process shifts to increase autonomy and collaboration.Top areas leaders believe will improve both developer productivity and satisfaction*multiple choice questionUsing AI automations(37%)Providing new collaboration tools(37%)Risk-taking and experimentation(36%)Streamlining decision-making(35%)Hosting hackathons(34%)010302040%41%of organizations are focused on measuring developer productivity,while 49%are focused on developer satisfaction.of organizations use tools that measure developer productivity to assess the satisfaction of their development teams.51%STATE OF DEVELOPER EXPERIENCE REPORT 20248IDC predicts that organizations worldwide will spend$40 billion on GenAI tools this year.This investment will quadruple to$151 billion within three years.According to our survey,leaders believe using AI to automate processes and testing is the most effective way of improving developer productivity and satisfaction.While much of the current AI focus is on helping developers save time in their code editors,AI shows potential to improve daily developer workflows by addressing tech debt,translating requirements,documentation gaps,and reducing interruptions.However,most developers are underwhelmed when asked to what degree AI-based dev tools improve personal productivity:30%said not at all,while 32%said only slightly.of developers are seeing more than a moderate productivity improvement from AI-based dev tools,despite leaderships belief that using AI is the most effective way to improve developer productivity.How much AI tools are improving developer productivity todayHow much AI tools will improve developer productivity within the next two yearsNot at all(30%)Slightly(32%)Moderately(22%)Very(11%)Extremely(5%)05151020253035%Not at all(12%)Slightly(27%)Moderately(35%)Very(20%)Extremely(6%)05151020253035%38%STATE OF DEVELOPER EXPERIENCE REPORT 20249Developers are more optimistic that AI tools will improve their productivity in the future,with 35%moderately convinced and 26%very or extremely convinced.But this is still less than software developer leaders,who all believe AI will improve the developer role.AI can help improve developer experience,but it cant solve all the pain points of development teams to improve productivity and satisfaction.Its critical for leaders to ask developers about their friction points and then focus on implementing the right tools and cultural changes to make a difference.Learn moreHow to measure GenAI adoption and impactThis guide from DX explains how to integrate GenAI into your software development process in a data-driven way and measure its impact on your business.Interest in developer experience is growing,but efforts are laggingProviding a great developer experience can be an effective recruitment and retention tactic.63%of developers said developer experience is important or very important when deciding whether to stay in their current job.While 86%of leaders believe that attracting and retaining the best talent will be nearly impossible without improving developer experience,less than a quarter of developers(23%)are happy with their teams investment in this area.The existence of this gap isnt surprising;it can be difficult to budget for new tools and get time to tackle tech debt.of developers are satisfied with the amount of time spent on improvements.Both developers and leaders know developer experience is important for attracting and retaining talent.23%STATE OF DEVELOPER EXPERIENCE REPORT 202410Leaders take:Attracting and retaining the best developer talent will be near impossible without improving the developer experienceHow important developer experience is to developersStrongly disagree(4%)Somewhat disagree(10%)Somewhat agree(43%)Strongly agree(43%)0 10 20 30 40 50%Not important(3%)Slightly important(7%)Moderately important(27%)Important(40%)Very important(23%)0 10 20 30 40 50%Developer satisfaction with time spent on developer experience improvementsVery unsatisfied(7%)Unsatisfied(30%)Neutral(40%)Satisfied(20%)Very satisfied(3%)0 10 20 30 40 50%STATE OF DEVELOPER EXPERIENCE REPORT 202411As our survey shows,almost two out of three developers consider leaving their roles when they arent satisfied with the developer experience at their organization.But theres hope.76%of organizations plan to invest more in developer experience within the next year,and according to our survey,that investment is poised to pay off.We cross-referenced two survey questions we asked developers:1.How satisfied are you with the amount of time your organization spends on developer experience improvements?2.In a typical week,what per