Fast & Free Shipping in UAE Free Returns Customer Support
Binge UAE
Price AED 73.52 In Stock

Estimate to be delivered 24 Sep - 27 Sep


Winner of the Shingo Publication AwardAccelerate 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 readers to apply in their own organizations.Readers 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.

Customers Reviews

I have revised my review and upgraded it based upon feedback...

4.0 out of 5.0 by David P. Graf on October 9, 2018
When I originally posted my review, I said that I would be glad to amend or even delete it based upon my concerns being answered or their being shown to be incorrect. One of the authors, Jez Humble, took the time to respond to me. I still have some lesser concerns but I am satisfied by his response. There was peer review of the research and DORA was not formed until after the research had been submitted for review. Since I was wrong about those points, I have upgraded my rating and have revised my review which starts in the next paragraph.Note that I make no claim to be as skilled when it comes to research as is Forsgren. Hands down, she has an impressive resume and experience which makes me look like what you scrape off the bottom of your shoe in comparison. When I approach this book and the research, I am concerned regarding the use of Snowball research. However, I recognize how hard it is to conduct research in the workplace and the so-called "real world" outside the laboratory. When reading this book, my main point would be to keep in mind what the authors openly say, to their credit, that the research presented does not lead itself to predictive or causal analysis. However, it can be used to draw inferences that those implementing DevOps can find very valuable. Use this book to expand your ideas of how to improve software delivery.
Buy Accelerate and begin your DevOps Transformation today--the whole company will thank you.

5.0 out of 5.0 by M. Wilson on April 13, 2018
I’ve lived in and consulted for many companies that would benefit from transforming their culture. If you are a leader in a company, and you 1) want to validate perceptions of company performance from the inside, and 2) want to continuously improve, read on.“The most innovative companies and highest-performing organizations are always striving to be better. High performing companies have 46 times more frequent code deployments, 440 times faster lead time from commit to deploy, 170 times faster mean time to recover from downtime, and 5 times lower change failure rate (1/5 as likely for a change to fail).”The reasons for embarking on this DevOps journey of acceleration and transformation are many. Leaders who want to realize this level of performance will get more loyalty and work out of their current people and attract awesome new ones. They will build better, more secure software--and a mature software delivery capability provides a competitive advantage to any business. This book provides evidence and research to back these assertions.Accelerate offers clear and compelling guidance to begin this shift no matter a company’s current level of maturity, covering the spectrum of roles from leaders to doers, from coders to architects to managers. If you are pressed for time, chapters are focused and easy to consider in turn, and provide excellent implementations recommendations.Leaders will be especially inspired by Part 3, a case study about a real Transformation. It all started by the willingness to change.DevOps is a cultural movement that feeds value delivery and growth within an organization. If you are responsible for any aspect of building secure, resilient rapidly evolving distributed systems, buy this book! Read it on your next plane ride and begin your journey of differentiation and transformation with the inspirational and executable guidance it offers.
Good But Not Great

3.0 out of 5.0 by Tiglath on June 18, 2019
I read this book to complete the DevOps picture from the manager's and the architect's point of view.As DevOps engineer and developer with 30 years of experience, I find hard to stomach the notion supported by this book that developers should be free to choose their tools. The book goes on to assure us that the upside of doing so far outweighs the downside. I strongly disagree.There is a thing called 'technical debt,' which is the sum of time and effort one has to pay to keep up with the tools one is 'married' to. To master a tool one has not only to learn the first version encountered but also those that follow in its evolution, and track new and discontinued capabilities during the course of the tool's life. This happens whether you learn C, Python, Java, or any other substantial language and tool in which one needs to remain proficient.Now imagine multiple projects using languages and tools at the whim of the team members. The overall list of technologies in use would be a long open-ended list in no time. What skill requirements do you pass on to HR to recruit new talent? How many candidates will be a good match for your large list of technical requirements?The argument in favor of such dangerous freedom is that otherwise developers may have to use tools they hate.Choosing the staff and the tools of a project requires careful consideration. It's at this point that you choose the best possible match. Consult the team members if you will, but it should not be up to them to decide, but to the project leader. Otherwise imagine if Team A chooses Confluence for documentation, while Team B uses Office 360, and yet Team C goes for TEX. After a few years you will have a rainbow of documentation formats. How is that better than having a consistent one?Developers like to use the tools they mastered, when not looking to learn a new one, and yes that is important, but what you do is to group people with skills pertinent to the project from the outset, so nobody will hate it.This notion that developers should be the ones choosing a project's technologies, really broke the spell of this book for me. How could they say that, and what sort of measurements did lead to such result?
Great blend of SW Delivery Excellence wrapped around Technical Practices and Leadership Foundation

5.0 out of 5.0 by JamesH on March 27, 2018
Great practical blend of leading thoughts around how you create and continuously evolve Software Delivery Excellence.Covers the 24 capabilities, the four true measures that align to tempo and stability, and introduces the Westrum model and Continuum.Combines Lean Software Development, Phoenix Project, DevOps Handbook and several concepts from different books around Lean Management and Practices.. marrying culture, DevOps and lean in one.Includes research methods and a data section.. and examples of how to measure stressing this is a journey that can’t be outsourced, and needs to grow within continuously to be competitive and thrive.