Accelerate: Building and Scaling High-Performing Technology Organizations
- Downloads：1391
- Type：Epub+TxT+PDF+Mobi
- Create Date：2021-03-05 03:19:20
- Update Date：2025-09-06
- Status：finish
- Author：Nicole Forsgren
- ISBN：B07BLYJ4HR
- Environment：PC/Android/iPhone/iPad/Kindle
- Download
Summary
Accelerate your organization to win in the marketplace。
How can we apply technology to drive business value？ For years we've been told that the performance of software delivery teams doesn't matter - that it can't provide a competitive advantage to our companies。 Through four years of groundbreaking research to include data collected from the State of DevOps reports conducted with Puppet， Dr。 Nicole Forsgren， Jez Humble， and Gene Kim set out to find a way to measure software delivery performance - and what drives it - using rigorous statistical methods。 This book presents both the findings and the science behind that research， making the information accessible for listeners to apply in their own organizations。
Listeners will discover how to measure the performance of their teams and what capabilities they should invest in to drive higher performance。 This book is ideal for management at every level。
How can we apply technology to drive business value？ For years we've been told that the performance of software delivery teams doesn't matter - that it can't provide a competitive advantage to our companies。 Through four years of groundbreaking research to include data collected from the State of DevOps reports conducted with Puppet， Dr。 Nicole Forsgren， Jez Humble， and Gene Kim set out to find a way to measure software delivery performance - and what drives it - using rigorous statistical methods。 This book presents both the findings and the science behind that research， making the information accessible for listeners to apply in their own organizations。
Listeners will discover how to measure the performance of their teams and what capabilities they should invest in to drive higher performance。 This book is ideal for management at every level。
Reviews
Ernestas Poskus
，
As former SRE highly recommend this for non technical leads and product managers。
Herman Seip
，
Probably one of the most influential books in my career。 Along with: "The state of devOps 2018++" Probably one of the most influential books in my career。 Along with: "The state of devOps 2018++" 。。。more
Toby
，
Hesitated to read this， thinking it might be a tedious restatement of the state of dev ops reports。 I was wrong， the book adds a lot more information， with data to back up what skilled and experienced practitioners have known for years。 This book will drive a lot more change because the deep research validates ideas beyond the level of “someone’s opinion”。 Really interesting to see how specific practices influence others， giving a roadmap to guide where your organization should focus first。 If y Hesitated to read this， thinking it might be a tedious restatement of the state of dev ops reports。 I was wrong， the book adds a lot more information， with data to back up what skilled and experienced practitioners have known for years。 This book will drive a lot more change because the deep research validates ideas beyond the level of “someone’s opinion”。 Really interesting to see how specific practices influence others， giving a roadmap to guide where your organization should focus first。 If you’re short on time， Part 1 is sufficient to read。 It’s the meat of the findings。 Part 2 describes the research approach which makes the findings more convincing。 Part 3 is 。。。more
Kevin Gough
，
Essential reading for anyone involved in software development。An easily digestible summary of the huge amount of research carried out by Forsgren et al。 If you are involved in the leadership of software development teams this will arm you with the evidence that you need to understand how and where you can help them improve。 Inspirational and convincing， while there may be nothing new here for those who are already on a devops journey， it is a compelling summary of why that journey is important。
Birkan
，
DevOps konusunda bir kitap okuma niyetiyle başladığım kitap bir noktadan sonra DevOps konusunda nasıl anket yapılıra doğru kaydı。 DevOps başlıkları ile ilgili kısım ise gereğinden fazla uzatılmış， sadece ekler bölümünü okuyup kitabın özetini alıp bir sonraki kitap ile yolunuza devam edebilirsiniz。
Muhammad
，
*the* critical handbook for a software practitioner/leader A great summer of 24 practices， backed with data， analysis and fantastic commentary that when implemented well， can really change the way your company makes better， faster and happier software
Matt Poland
，
If you want to learn about how to do surveys on organizations， read this book。 If you want to learn about DevOps， look elsewhere。
Laura
，
Not a lot of new-to-me information but solid foundational read。
Dana
，
Our manager is passionate about it， and I see why。The book contains thoughts-triggering ideas， reveals a couple of curious statistical correlations， is very descriptive about the methods chosen for the research。 Though， it was a bit hard to read: most of stuff felt too obvious， and explained too broadly。Hope it just means that our team/organization is making some good job here if all the principles and suggestions felt to me like 'Yeah makes sense but we already know about it and strive for it'。 Our manager is passionate about it， and I see why。The book contains thoughts-triggering ideas， reveals a couple of curious statistical correlations， is very descriptive about the methods chosen for the research。 Though， it was a bit hard to read: most of stuff felt too obvious， and explained too broadly。Hope it just means that our team/organization is making some good job here if all the principles and suggestions felt to me like 'Yeah makes sense but we already know about it and strive for it'。Worth having a look。 。。。more
Rémi
，
If you are a tech lead， a software developer， an architect， or a DevOps guy， or interested in ！ you need to read this book
Terje Fjeld
，
Perfect Book - red after Teams Toplogies
Mickaël A
，
Very good approach to link DevOps practices to organization performance。 It is really enlightning， useful and quite practical。 I found the second part "research" a way to big and less interesting as we are not reading this book to learn about how to conduct studies。If you have little time， read chapter 4 and Appendix A which are a good summary of the book。 Very good approach to link DevOps practices to organization performance。 It is really enlightning， useful and quite practical。 I found the second part "research" a way to big and less interesting as we are not reading this book to learn about how to conduct studies。If you have little time， read chapter 4 and Appendix A which are a good summary of the book。 。。。more
David Carpinteiro
，
I started reading this book because of interest in the topics and the authors behind it， also when Martin Fowler is involved， almost for sure something good is to be expected。 At least this was my expectation but as i was reading soon my expectation went down the drain。I can't consider this as a book， this is a study that basically the three appendixes in the end of the book quite resume everything and the rest tries to extend each topic with some ideas and suggestions， but mostly references of I started reading this book because of interest in the topics and the authors behind it， also when Martin Fowler is involved， almost for sure something good is to be expected。 At least this was my expectation but as i was reading soon my expectation went down the drain。I can't consider this as a book， this is a study that basically the three appendixes in the end of the book quite resume everything and the rest tries to extend each topic with some ideas and suggestions， but mostly references of how the content on the book was reached through a serious of studies and the methods to obtain them。I'm not saying that what is here described relative to devops， lean and the idea to have a more high performing technologically organization is rubbish， is quite the opposite。 Everything here described i agree， i relate to and definitelly will try to use some of the ideas。 What i don't agree is to have to buy this， that is supposed to be a book but at the end what i bought was actually a study， hard and difficult to read。Really was expecting more from this authors and from all the names in the cover。 。。。more
Piotr
，
In my opinion too much book is focused on explaining the research methodology behind their research， and too little on the actual development practices that can make your organization high performing。 But this could be me approaching this book with a wrong expectations。 Still， the parts of the book focused on the actual practices were pretty cool。
Elizabeth
，
This is a glorified statistics report。 I haven't read "The State of DevOps" report yet， but I imagine it said all this book said， in a more succinct manner。 What they had to say was important， and I agree with their research that if the technology in your organization doesn't follow these practices， you'll be left behind。But oh my goodness， how they said it。 It was awful; you can tell these folks are used to writing statistical reports。 They laboriously said "This is what we will show you。 This This is a glorified statistics report。 I haven't read "The State of DevOps" report yet， but I imagine it said all this book said， in a more succinct manner。 What they had to say was important， and I agree with their research that if the technology in your organization doesn't follow these practices， you'll be left behind。But oh my goodness， how they said it。 It was awful; you can tell these folks are used to writing statistical reports。 They laboriously said "This is what we will show you。 This is what we are showing you。 This is what we showed you" to the point I wanted to claw out my eyes。 They also use very generic terms that don't hold their specific meaning very well。 For example， immediately they define 24 practices （but call them capabilities） of organizations with an innovative culture。 I hate the use of "capability" used as more of a noun than an adjective: "capability" should be the degree to which you can accomplish X， not X itself。 （They should've used "practices" or "indicators"。） Similarly， they discuss Westrum's organization construct， which to me is on a spectrum; you either fall to the left/poor/pathological ranking on the construct， or you fall to the right/good/generative ranking。 I guess they say that generative company cultures are Westrum organizations。 *shrug*The diagrams were simple enough to be inane， as they were little boxes with arrows that repeated what the text said without any further illumination。 I also found that they explained the wrong things; I didn't need to be reminded of the difference between primary and secondary research， but a definition of what they considered to be lead time would've been helpful。 And though it was helpful to discuss latent constructs and manifest variables， they didn't need to define manifest variables twice within three pages。 （I think they needed a human， not a statistician， to write this book。）The third part was alright。 It was necessary， to flesh out their statements into a Real Book， and illustrate how their findings can work in a real company。 ING sounds like a fun place to work。Publishing the book seems like a cash grab。 And， Jeff Sutherland's Art of Doing Twice the Work in Half the Time was a more engaging read。 I'd say their both content is on the same level of importance， though。 That goes to show you how important writing and presentation are。 。。。more
Mark Robinson
，
An excellent introduction and summary of how to create high performing teams with technology。 Solid advice and all of it data driven。
Leni Kadali
，
Will definitely be re-reading this one。 Lots of great nuggets to chew on for the future。
Yevgen Polyak
，
Great book with comprehensive analysis。 However， you could easily half it and get the same ideas in a format where you can easily refer to those ideas。
Simon
，
Really important research to help understand the impact of team culture， tooling， psychological safety， automation and workflows on software team performance and morale。
Vishal Biyani
，
I don't know why did I put off this book so far but once I read it I realized the value it brings to any enterprise transformation。 The research and the 23 factors are very well done。 The book can get a bit slow at times because discussing such abstract topics can be hard at times。 The book is as impactful as the CI/CD books by Jez Humble。 I don't know why did I put off this book so far but once I read it I realized the value it brings to any enterprise transformation。 The research and the 23 factors are very well done。 The book can get a bit slow at times because discussing such abstract topics can be hard at times。 The book is as impactful as the CI/CD books by Jez Humble。 。。。more
Huss
，
On my cubicle’s desk， on the 13th floor of a global financial institution， I arranged a black wooden shelf with books pertaining to the management of technical projects。 “Accelerate” is the first book that I arbitrarily picked up from that shelf （which， I must mention， is a sheld that is home to a beautiful Levistona， an Overwatch Lego figure， and a matte black silently-ticking clock）。 Having spent most of my career by far at a start-up， I never realized the gap I had in understanding and managi On my cubicle’s desk， on the 13th floor of a global financial institution， I arranged a black wooden shelf with books pertaining to the management of technical projects。 “Accelerate” is the first book that I arbitrarily picked up from that shelf （which， I must mention， is a sheld that is home to a beautiful Levistona， an Overwatch Lego figure， and a matte black silently-ticking clock）。 Having spent most of my career by far at a start-up， I never realized the gap I had in understanding and managing tech projects and infrastructure in organizations。 When measuring performance of any technical project， key indicators are: t1。 Lead-timet2。 MTTRt3。 Deployment Frequencyt4。 Change-Fail rate 。。。more
Khyati Shah
，
Might have been a game changer two years ago but as of today， most of the recommended practices in this book are already mainstream。 I also found the book a little repetitive。
Aksel Nooitgedagt
，
I'm very happy that I was recommended this book。 It's a perfect guide for me and our team to discover which areas should we work on， to be better performing。Key takeaway for me will be that in every project， we can measure how well performing we are by checking how is our:- Lead Time，- Deployment Frequency，- Mean Time to Restore （MTTR） and- Change Fail Percentage。I'm also very thankful for Appendix A - a list of 24 key capabilities that drive improvements in software delivery。 I think we'll gath I'm very happy that I was recommended this book。 It's a perfect guide for me and our team to discover which areas should we work on， to be better performing。Key takeaway for me will be that in every project， we can measure how well performing we are by checking how is our:- Lead Time，- Deployment Frequency，- Mean Time to Restore （MTTR） and- Change Fail Percentage。I'm also very thankful for Appendix A - a list of 24 key capabilities that drive improvements in software delivery。 I think we'll gather the devs in the new year to go through the list and think about what we can improve。 。。。more
Diego Pacheco
，
I'm doing and following the DevOps movement since 2011。 So for me， there was not big news。 However， that does not make the book bad。 Every book that talks good about Architecture， CI/CD， and especially Lean and is against maturity models and BI-MODALS have my respect :-）。 It's short but very data-driven。 I'm doing and following the DevOps movement since 2011。 So for me， there was not big news。 However， that does not make the book bad。 Every book that talks good about Architecture， CI/CD， and especially Lean and is against maturity models and BI-MODALS have my respect :-）。 It's short but very data-driven。 。。。more
Francisco
，
Good bookThis is a good book to integrate an agile culture and mindset with the importance of devops and good technical pratices based on an experience research。
Tomer Levy
，
A good read， helped me organize my thoughtsI enjoyed reading this book。 There was nothing completely new， but it organized it all in a logical framework that helped me。I took many notes and to-do's。The book offers surveys as the main tool to measure current state and progress。 Even though the logic for that is explained in chapter 13 and 14， I expected other more objective KPI's。 A good read， helped me organize my thoughtsI enjoyed reading this book。 There was nothing completely new， but it organized it all in a logical framework that helped me。I took many notes and to-do's。The book offers surveys as the main tool to measure current state and progress。 Even though the logic for that is explained in chapter 13 and 14， I expected other more objective KPI's。 。。。more
Charles Guo
，
This is a great book if you're looking for a summary of where the conventional wisdom currently is in tech。 Unfortunately， it's not a great book if you're looking for an evidence-based， cautious， even-handed， scientific case for why that conventional wisdom reflects best practices。 It's filled with the sort of too-pretty charts and diagrams that often plague business- or thought-leadership-oriented books。 This is a great book if you're looking for a summary of where the conventional wisdom currently is in tech。 Unfortunately， it's not a great book if you're looking for an evidence-based， cautious， even-handed， scientific case for why that conventional wisdom reflects best practices。 It's filled with the sort of too-pretty charts and diagrams that often plague business- or thought-leadership-oriented books。 。。。more
Alex Kondov
，
I heard a lot of praise about this book but it didn’t live up to my expectations。 It’s written in a way that resembles an academic paper and presents a collection of truisms and surface level advice。The point it tries to get across is that continuous delivery would greatly improve any organisation。 It goes into detail of how the authors reached that conclusion and their research methods - that’s about it。 The actionable advice seemed shallow to me。
Valerie
，
Dry to say the least， and not a book that made me want to put it down and get to work implementing it unfortunately。 But a relatively quick read， and I found the Appendices extremely useful for highlighting the key takeaways。 I look forward to using the info， since it is potentially very powerful。
Hammad Aslam
，