Boost Your Thinking.
Transform Your Life

Subscribe to Thinking Hacks, our free weekly newsletter now.

Boost Your Thinking.
Transform Your Life

Subscribe to Thinking Hacks, our free weekly newsletter now.

Boost Your Thinking.
Transform Your Life

Subscribe to Thinking Hacks, our free weekly newsletter now.

Mental Models
Featured Models

DevOps Mindset

Development and operations teams both care about their customers. However, while dev teams strive for rapid product improvements, ops teams are typically focused on delivering a stable, reliable customer experience — often putting the teams at odds. Embracing a DevOps Mindset involves delivering greater customer value by better integrating the work of development and operations teams. It incorporates a loose set of principles that encourages all teams to own the end-to-end process by leveraging greater collaboration, shared tools, automation, continuous monitoring, and continuous improvement.  YES, IT’S ABOUT DESTROYING THOSE DAMN SILOS. DevOps has become the standard practice of big tech and startups alike, though it remains a broad movement rather than a strictly defined approach. That said, implementing DevOps tends to begin with culture, leverages technology, and includes working to increase:  Collaboration and breaking down of silos: with cross-functional teams and greater inter-team transparency. This is in part cultural but will likely incorporate processes and team structure for improved collaboration.  Automation & streamlining: including using standardised tools between teams, and automating processes.  Continuous delivery: with small, gradual changes rather than large, infrequent builds — thus embracing continuous integration and deployment for ongoing and continuous improvement.  Accepting failure as normal: providing the systems and culture to address inevitable problems quickly.  Embed and amplify feedback loops: measuring, monitoring, and logging results to provide continuous feedback. This also includes incremental experiments.  Systems thinking and taking end-to-end responsibility: challenging the idea of ‘throwing a build over the wall’ and moving towards habitually 'viewing the whole' and taking responsibility for the entire lifecycle. DEVOPS AND AGILE  On a simplistic level, whereas Agile Methodology sets out to deliver greater value by iterating and supporting adaption, DevOps sets out to deliver greater value by better managing and combining the end-to-end process from delivery to operations. Rather than an alternative to Agile, DevOps is generally implemented as a means to extend Agile beyond traditional software and dev teams — See Origins below for more. 'EVERYTHING-OPS'… REALLY? Like Agile, DevOps was originally created by and for engineering teams and is already having ramifications on broader business practice.  Practitioners point out that DevOps is not just about development and operations teams but often involves management, testers, QA, security, data, and other domains. Indeed, it’s tending to spawn a range of related terms:  SecOps/ DevSecOps: which involves integrating security as central to the lifecycle rather than an afterthought.  BizOps/ BizDevOps: aims to connect business operations and technology, development, and operations for greater inter-department transparency.  DataOps/ DataDevOps: integrating data engineering and analytics into the DevOps approach.  ChangeOps: The State of DevOps Report 2020 goes into considerable detail about the need to integrate a DevOps approach with change management, see the In Practice section below for more.  In addition, there’s WinOps, which is Microsoft’s brand of DevOps and Site Reliability Engineering (SRE), which was developed by Google in 2003, predating DevOps and generally viewed as a specific application of its principles. While there's more that could be said about the tech version of DevOps (such as Microservices, tech tools etc), we've focused on the more transferable elements, especially in the Actionable Takeaways below.   IN YOUR LATTICEWORK.  We’ve already talked about how a DevOps Mindset links to Agile Methodologies, including Scrum and Kanban, and it's also in part inspired by Lean Thinking. Most practitioners stress that the cultural change and team dynamics that underpin a DevOps Mindset will require Psychological Safety, including practices such as ‘blameless postmortems.’ Cross-functional collaboration at the heart of DevOps will also benefit from T-Shaped People and can be informed by the 5 Stages of Teaming.

Explore Mental Models

What are Mental Models?
Categories:

Subcategories:

No Mental Model Available

Related content