Other Sellers on Amazon
Download the free Kindle app and start reading Kindle books instantly on your smartphone, tablet or computer – no Kindle device required. Learn more
Read instantly on your browser with Kindle Cloud Reader.
Using your mobile phone camera, scan the code below and download the Kindle app.
Enter your mobile phone or email address
By pressing ‘Send link’, you agree to Amazon's Conditions of Use.
You consent to receive an automated text message from or on behalf of Amazon about the Kindle App at your mobile number above. Consent is not a condition of any purchase. Message and data rates may apply.
Accelerate: The Science of Lean Software and Devops: Building and Scaling High Performing Technology Organizations: The Science of Lean Software and ... HighPreforming Technology Organizations Paperback – Illustrated, 1 June 2018
Enhance your purchase
Frequently bought together
"Excellent! As well as conclusively showing that DevOps outcomes are faster, cheaper AND safer, this book is an excellent case study for robust survey design and analysis."--Adrian Cockroft
"We strongly recommend this book to anyone involved in a digital transformation for solid guidance about what works, what doesn't work, and what doesn't matter."--Tom & Mary Poppendieck, Authors of the Lean Software Development Series
About the Author
- Publisher : IT Revolution Press; Illustrated edition (1 June 2018)
- Language : English
- Paperback : 288 pages
- ISBN-10 : 1942788339
- ISBN-13 : 978-1942788331
- Dimensions : 14.96 x 2.16 x 23.09 cm
- Best Sellers Rank: 2,209 in Books (See Top 100 in Books)
- Customer Reviews:
About the authors
Review this product
Top reviews from Australia
There was a problem filtering reviews right now. Please try again later.
Top reviews from other countries
It had some new pieces of advice and guidance for me, and I especially like how it brings all together the best and well established practices, but generally it didn’t offer me much, but maybe I’m not the intended audience? This would be a great book if you were a struggling CTO or someone stuck in the old ways of manual testing etc. If you run a failing IT company or department then by all means read this, but to the established folks already doing the right things then pick this up 2nd hand on the cheap.
1. It is short enough and accessible enough to be reasonably recommended to and consumed by a range of roles outside of the technology function.
2. It is written by and recommended by a number of people who clearly know their onions: Jez Humble, Nicole Forsgren and Gene Kim are all multipublished, award winning authors who have been involved in the State of DevOps survey for an extended period of time. Martin Fowler (who writes a forward) is one of the founding fathers of Agile and has written profoundly on many aspects of the programming craft
3. It seeks to justify its assertions with a range of quantitative methods which are pitched at the right level…you could use these ideas both to structure a business case and as a measurement framework to report against it.
4. It explores a range of technical, organizational, managerial and cultural aspects that combine to provide a step change in software development capability. It isolates atomic drivers of improvement. It describes positive and negative feedback loops to be aware of.
5. It connects those ideas into a coherent programme and suggests how you might go about adoption.
Apart from all of the practical ideas and the way it connects them I think the most interesting thought it left me with was this. Not only is high performance in the technology space going to offer a key differentiator for businesses in the future but that high performing technology function can be a catalyst to a high performing organization full stop.
It's a study of thousands of companies, the development practices they use and whether they succeed or not.
It's the closest thing I've seen to evidence that doing things the "right" way is a key contributor to business success. Teams that deploy more often have better success. Organizations that are safe to work in (where you can raise concerns without fear of being fired) have better success.