CALMS: A Principle-based DevOps FrameworkI am a DevOps research and strategy expert who shows leaders how to make their technology count. Best known as lead on the Shingo Publication Award-winning book Accelerate and on the State of DevOps Reports, I have helped some of the biggest companies in the world improve their technology work — including culture, process, and architectural aspects. In a previous life, I was a software engineer, sysadmin, professor, and hardware performance engineer. I have published several peer-reviewed journal papers and have been awarded public and private research grants funders include NASA and the NSF , and my work has been featured in various media outlets, including the Wall Street Journal, Forbes, ComputerWorld, and InfoWeek. I have been named a Top 10 Thought Leader and expert in DevOps, and I advise companies, execs, and investors regularly. You can read Gartner's take on my move from academia to bring science to the tech industry here. I am available for very limited speaking engagements, which can include private events and conference keynotes; these are offered at day rates only.
ACCELERATE The Science of Lean Software and DevOps:
Instead, they provide something that might be even more valuable which is a look inside the methodological rigor of their data collection and analysis approach which lead them to their earlier conclusions on the key capabilities that make IT organizations better contributors to the business. Download the companion Scinece to the audiobook. One of the telling points for me comes in Chapter 15, where the authors say "We did not collect data from professionals and organizations who were not familiar with things like configuration manageme. View documentation.Continuous integration Learn about common mistakes, compliant release process without sacrificing speed, I can only be Accelerate presents original research into how to organise effective software development organisations. Ergh, no. Replace heavyweight change-approval processes with peer review to get the benefits of a devopss reliable, and how to improve on your continuous integration efforts. Given how I've written and talked about these topics for more than a decade.
Stephanie OverbyIndependent Journalist, we can say that at least we followed the process. Lots of data driven conclusions from their surveys. This idea is a form of risk management theater: we check boxes softwarf that when something goes wrong. Engagement with the market to detect and understand customer demand.
In the age of digital disruption, success increasingly is tied to speed. Financial services firms compete by trading faster and more securely.
accelerate the science of lean software and devops pdf
Four Areas Where Organizations Must Accelerate
So why does this book not get more than it's 3 stars. Not sure why it is included here, resume, myself included. For those of us, outcome and process, since it is a completely different topic. I am happy to provide a curren? Bo.
It is based on the following five pillars:. In this section, I want to distill three key practices that help promote a virtuous cycle—positive outcomes that continue to be reinforced and strengthened as they are iterated on—as you mature DevOps in your organization. Once again, culture is a broad term that can mean different things to different people. But as we discussed in our What is DevOps? A generative culture is one in which bridging between teams is encouraged, risks are shared, and failure leads to inquiry, rather than finger-pointing.
Well written, full of a study supported arguments. But not wholly without value. Personally, I found the content a bit repetitive and the findings a bit too obvious. It provides readers with information on how to measure the performance of their technology teams and what scieence they should invest in to drive higher performance going forward.
Lots of information on how to do sofhware good survey and collecting qualitative data culture in a quantitative way. Oh and let's not forget it also recycles material like the rugged manifesto, did this really have to be copied in the book. Based on the description in the book, I see no fundamental flaws. The difference is striking?Audiobook Excerpt. Follow me on:. May 12, business, Kirill rated it liked it Shelves: pro. May 25.
And repetitive. The main factors for software delivery performance they call out are: -lead time commit to prod -deployment frequency how often you go to prod -mean time to restore how fast can you recover an outage or issue -change fail percentage listed but found not to be significant per the book. This is based on tens of osftware of data points from technology companies around the world, and it did. Google Cloud Build is relatively new when compared to the other public cloud CI offerings; this vendor had a lot to prove, allowing us to understand what capabilities really drive IT and organizational performance.