I am a practitioner and developer of the OPE loop: observe, position, execute. I have used the OPE loop for over 20 years in every facet of my life.
Experimentation is important because 33.33% of the time you will get one of the follow: good results, bad results, indifferent results. If 66.66% of the time you’ll not get improvement, you need velocity to fail fast and pivot. Tweet this
DevOps is the convergence of people, process, and products that deliver value to end users and solution stakeholders.
In 2016 DevOps evolved from a niche practice to mainstream employed by 25% of global 2000 organizations. If you are not doing it, your competitors are. Tweet this
The fifth annual State of DevOps Report offers a close-up view of deployments, security, stability and employee loyalty at organizations that have (and haven’t) successfully adopted DevOps practices. Here is what the report states:
- High-performing IT organizations deploy 200 times more frequently than low performers, with 2,555 times faster lead times.
- They have 24 times faster recovery times and three times lower change failure rates.
- High-performing IT teams spend 50 percent less time remediating security issues.
- And they spend 22 percent less time on unplanned work and rework.
- Employees in high-performing teams were 2.2 times more likely to recommend their organization as a great place to work.
- Taking a lean approach to product development (for example, splitting work into small batches and implementing customer feedback) predicts higher IT performance and less deployment pain.
I highly recommend that people read The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win. Its the ultimate case study in taking a failed project and turning it around.