Accelerate (book)

Add links
From Wikipedia, the free encyclopedia
Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
Cover
AuthorNicole Forsgren, Jez Humble, Gene Kim
CountryUnited States
LanguageEnglish
SubjectDevOps
PublisherIT Revolution
Publication date
2018
Pages156 (paperback)
AwardsShingo Prize[1][2]
ISBN9781942788331
OCLC1035781633

Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations is a software engineering book co-authored by Nicole Forsgren, Jez Humble and Gene Kim.[3] The book explores how software development teams using Lean Software and DevOps can measure their performance and the performance of software engineering teams impacts the overall performance of an organization.[4][5]

The work in the book contains research conducted by Google's DevOps Research and Assessment (DORA) team for State of DevOps Reports. Before being acquired by Google, DORA conducted this research for the DevOps company Puppet and later became an independent team (with Puppet continuing to produce reports by a new team).[6][7]

Four Key Metrics[edit]

The authors examine 23,000 data points from a variety of companies of various different sizes (from start-up to enterprises), for-profit and not-for-profit and both those with legacy systems and those with modern systems.[8][9][10]

The four metrics identified are as follows:[11][5]

  • Change Lead Time - Time to implement, test, and deliver code for a feature (measured from first commit to deployment)
  • Deployment Frequency - Number of deployments in a given duration of time
  • Change Failure Rate - Percentage of failed changes over all changes (regardless of success)
  • Mean Time to Recovery (MTTR) - Time it takes to restore service after production failure

The authors further measure how various technical practices (like outsourcing) and risk factors impact performance metrics for an engineering team.[12][13] These metrics can be crudely measured using psychometrics[14] or using commercial services.

Criticism[edit]

The computer scientist Junade Ali has criticised the research work in Accelerate (and the work in the DORA State of DevOps Reports) on multiple grounds.[15] Research conducted by Ali and the British polling firm Survation found that both software engineers (when building software systems) and public perception (when using software systems) found other factors mattered significantly more than the outcome measures which were treated as the "Four Key Metrics" (which ultimately measure the speed of resolving issues and the speed of fixing bugs, and are used to create the findings in the book), and risk and reward appetite varies from sector-to-sector.[16][17][18][19]

Additionally, Ali criticised how the research relies upon subjective measures to evaluate performance without controlling for cognitive bias (despite prior research showing software engineers overpredict performance) and methodology flaws which can lead to respondents rating factors in software quality and delivery speed as optimal on the basis that they are happy at their workplace (rather than critically evaluating the performance in particular domains).[20][21]

Ali has also criticised the research on the basis that reputable opinion polling firms who comply with the rules of organisations like the British Polling Council should publish their full results and raw data tables, which the DORA team did not do - and additionally that the sponsors of the polling (Google Cloud and previously Puppet) create products which have a vested interest in having software engineers deliver faster (despite research indicating high levels of burnout amongst software engineers), which the results of the research ultimately supported. Despite the authors arguing that speed of delivery and software quality go hand-in-hand, Ali has offered several counter-examples; including the comparatively high quality of aviation software despite infrequent changes, contrasted with rapid application development being pioneered in the software that resulted in the British Post Office scandal and agile software development being used in the software responsible for the 2009–2011 Toyota vehicle recalls.[22][23]

The software developer Bryan Finster has also discussed how, as correlation does not imply causation, organisations who are considered "high performing" in the research are not high performing because they focussed on the DORA metrics, but instead focussed on delivering value to users and arguing the metrics should be used as "trailing indicators for poor health, not indicators everything is going well".[24][25]

24 Key Capabilities[edit]

The authors outline 24 practices to improve software delivery which they refer to as "key capabilities" and group them into five categories.[26]

Continuous Delivery[edit]

  • Use Version Control for all Production Artifacts
  • Automate Your Deployment Process
  • Implement Continuous Integration
  • Use Trunk-Based Development Methods
  • Implement Test Automation
  • Support Test Data Management
  • Shift Left on Security
  • Implement Continuous Delivery (CD)

Architecture[edit]

  • Use a Loosely Coupled Architecture
  • Architect for Empowered Teams

Product and Process[edit]

  • Gather and Implement Customer Feedback
  • Make the Flow of Work Visible through the Value Stream
  • Work in Small Batches
  • Foster and Enable Team Experimentation

Lean Management and Monitoring[edit]

  • Have a Lightweight Change Approval Processes
  • Monitor across Application and Infrastructure to Inform Business Decisions
  • Check System Health Proactively
  • Improve Processes and Manage Work with Work-In-Process (WIP) Limits
  • Visualize Work to Monitor Quality and Communicate throughout the Team

Cultural[edit]

  • Support a Generative Culture
  • Encourage and Support Learning
  • Support and Facilitate Collaboration among Teams
  • Provide Resources and Tools that Make Work Meaningful
  • Support or Embody Transformational Leadership

References[edit]

  1. ^ "IT Revolution Announces 'Accelerate' Book Wins Shingo Publication Award". markets.businessinsider.com. Retrieved 5 April 2021.
  2. ^ "Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performance Technology by Nicole Forsgren, PhD, Jez Humble, Gene Kim, Steve Bell, and Karen Whitley Bell Receives Shingo Publication Award". Shingo Institute. 4 February 2020. Retrieved 5 April 2021.
  3. ^ "The 2018 InfoQ Editors' Recommended Reading List: Part One". InfoQ. Retrieved 5 April 2021.
  4. ^ Bloomberg, Jason. "Digital Influencer Nicole Forsgren: Bringing Science to DevOps". Forbes. Retrieved 5 April 2021.
  5. ^ a b Drugeot, Constance (30 March 2021). "Why is a DevOps assessment important, and how to do it right?". DevOps Online. Retrieved 5 April 2021.
  6. ^ "2023 State of DevOps". Splunk-Blogs. Retrieved 5 January 2024.
  7. ^ Anderson, Tim (6 October 2022). "State of DevOps report 2022: for secure software, team culture counts more than technology • DEVCLASS". DEVCLASS. Retrieved 5 January 2024.
  8. ^ Overby, Stephanie. "7 takeaways to "Accelerate" your DevOps". TechBeacon. Retrieved 5 April 2021.
  9. ^ Linders, Ben; Humble, Jez. "Q&A on the Book Accelerate: Building and Scaling High Performance Technology Organizations". InfoQ. Retrieved 5 April 2021.
  10. ^ Mangot, Dave (17 March 2021). "Get good at delivering software". CIO. Retrieved 5 April 2021.
  11. ^ "Are you an Elite DevOps performer? Find out with the Four Keys Project". Google Cloud Blog. Retrieved 5 April 2021.
  12. ^ Johnson, Emily. "Study: DevOps Outsourcing Can Cost You". InformationWeek. Retrieved 5 April 2021.
  13. ^ Doddi, Lakshmi (1 April 2021). "Book Summary: Accelerate — by Nicole Forsgren, Gene Kim, Jez Humble". Medium. Retrieved 5 April 2021.
  14. ^ Linders, Ben; Humble, Jez. "Q&A on the Book Accelerate: Building and Scaling High Performance Technology Organizations". InfoQ. Retrieved 5 April 2021.
  15. ^ Turner, Graham (20 November 2023). "Report: Software Engineers Face Backlash for Reporting Wrongdoing". DIGIT.
  16. ^ "75% of software engineers faced retaliation the last time they reported wrongdoing - ETHRWorldSEA". ETHRWorld.com. Retrieved 5 January 2024.
  17. ^ Saran, Cliff. "Software engineers worry about speaking out - Computer Weekly". ComputerWeekly.com. Retrieved 5 January 2024.
  18. ^ Woollacott, Emma (21 November 2023). "Workplace retaliation is stopping software engineers from speaking out over malpractice". ITPro. Retrieved 5 January 2024.
  19. ^ Mitchell, Sean. "Unethical activities found prevalent in UK software engineering industry". IT Brief UK. Retrieved 5 January 2024.
  20. ^ Prosser, David. "How To Avoid The Software Delays Holding Your Business Back". Forbes. Retrieved 5 January 2024.
  21. ^ "On DORA Metrics, SPACE and DevEx - DZone". dzone.com. Retrieved 5 January 2024.
  22. ^ "Overview of the Rules of Disclosure". British Polling Council. Retrieved 5 January 2024.
  23. ^ Hughes, Owen. "Developers are exhausted. Here's what needs to change". ZDNET. Retrieved 5 January 2024.
  24. ^ Finster, Bryan (29 March 2021). "5 Minute DevOps: The Metrics are Lying". Medium. Retrieved 5 January 2024.
  25. ^ Cummins, Holly. "Holly Cummins on X". X.com. Retrieved 5 January 2024.
  26. ^ "24 Key Capabilities to Drive Improvement in Software Delivery".

External links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Accelerate_(book)&oldid=1222907306"