yours," Aaron De Smet, Bonnie Dowling, Marino Mugayar-Baldocchi, Bill Schaninger, McKinsey, Sep 2021; "Yes, you can measure software developer productivity," Chandra Gnanasambandam, Martin Harrysson, Alharith Hussin, Jason Keovichit, and Shivam Srivastava, McKinsey, August, 2023.
development, testing, and management and 25% are utilizing machine learning with the greatest focus on leveraging AI to support DevOps analytics and process, governance, and security testing.
of their developers, but knowing how to measure or even define developer productivity has remained elusive.” The Problem “ Source: “DevEx: What Actually Drives Productivity," Abi Noda, Margaret-Anne Storey, Nicole Forsgren, Microsoft Research, Michaela Greiler, May 2023. “Programming productivity,” Wikipedia, accessed June 12th, 2024. there is no clear-cut definition of productivity and its influencing factors, although research has been conducted for more than a century. Like in software engineering, this lack of common agreement on what actually constitutes productivity, is perceived as a major obstacle for a substantiated discussion of productivity.” “
Nicole Forsgren ,Gene Kim, Jez Humble, Feb, 2021. “The SPACE of Developer Productivity," Nicole Forsgren, Margaret-Anne Storey, Chandra Maddila, Thomas Zimmermann, Brian Houck, and Jenna Butler, Jan-Feb, 2021. Also see: "Developer Thriving: The four factors that drive Software Developer Productivity across Industries,” and, low usage of DORA and SPACE at tech companies from Abi Noda, Jan, 2024. DORA SPACE
Storey, Nicole Forsgren, Microsoft Research, Michaela Greiler, May 2023. See earlier study: “The SPACE of Developer Productivity: There's more to it than you think," Nicole Forsgren, Margaret-Anne Storey, Chandra Maddila, Thomas Zimmermann, Brian Houck, and Jenna Butler, Jan-Feb, 2021. Happiness, flow, features Or, “stop interrupting me!”
Toil, Confusion, Blockers - What are we making? - We have a strong vision for our product, and we're doing important work together every day to fulfill that vision. - I have the context I need to confidently make changes while I'm working. - I am proud of the work I have delivered so far for our product. - I am learning things that I look forward to applying to future products. - My workstation seems to disappear out from under me while I'm working. - It's easy to get my workstation into the state I need to develop our product. - What aspect of our workstation setup is painful? - It's easy to run our software on my workstation while I’m developing it. - I can boot our software up into the state I need with minimal effort. - What aspect of running our software locally is painful? What could we do to make it less painful? - It's easy to run our test suites and to author new ones. - Tests are a stable, reliable, seamless part of my workflow. - Test failures give me the feedback I need on the code I am writing. - What aspect of production support is painful? - We collaborate well with the teams whose software we integrate with. - When necessary, it is within my power to request timely changes from other teams. - I have the resources I need to test and code confidently against other teams' integration points. - What aspect of integrating with other teams is painful? - I'm rarely impacted by breaking changes from other tracks of work. - We almost always catch broken tests and code before they're merged in. - What aspect of committing changes is painful? - Our release process (CI/CD) from source control to our story acceptance environment is fully automated. - If the release process (CI/CD) fails, I'm confident something is truly wrong, and I know I'll be able to track down the problem. - What aspect of our release process (CI/CD) is painful? - Our team releases new versions of our software as often as the business needs us to. - We are meeting our service-level agreements with a minimum of unplanned work. - When something is wrong in production, we reproduce and solve the problem in a lower environment. Sources: "Developer Toil: The Hidden Tech Debt," Susie Forbath, Tyson McNulty, and Coté, August, 2022. See also Michael Galloway’s interview questions for platform product managers.
29% 2021Q3 2022Q1 2023Q1 2023Q3 2024Q1 CI and CD Usage, 2021 to 2024 CD CI Question: Which of the following technologies have you used as part of your development activities in the last 12 months? Source: CD Foundation Surveys (Slashdata). Source: "State of CI/CD Report 2024: The Evolution of Software Delivery Performance," CD Foundation and SlashData, April, 2024, and previous studies.
71% 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% 2021Q3 2022Q1 2023Q1 2023Q3 2024Q1 CI Usage, 2021 to 2024 CI No CI Question: Which of the following technologies have you used as part of your development activities in the last 12 months? Source: CD Foundation Surveys (Slashdata). Source: "State of CI/CD Report 2024: The Evolution of Software Delivery Performance," CD Foundation and SlashData, April, 2024, and previous studies.
development, testing, and management and 25% are utilizing machine learning with the greatest focus on leveraging AI to support DevOps analytics and process, governance, and security testing. Source: “Applying Artificial Intelligence to Strengthen Application Development and Product Life-Cycle Management,” Pete Marston, IDC, Nov 2023 2023