Group items tagged

Much has been written on how to effect culture change in an organization. It's a large undertaking and difficult to know where to begin-or if, indeed, it's even possible. Anju Jain provides a brief and clear list of actions that you can take to get started.

"I have worked in environments where reacting was the "normal" way to approach issues and being proactive was just a waste of time... *facepalm* The seemingly simple idea of changing the workplace culture from reactive to proactive was hard to pitch, let alone implement on my own. 18 months ago, I knew there was a better way of doing things and I was determined to find something. I had been watching developers implement Agile Development processes with great envy and I was starting to see concepts that would have great outcomes if adopted in a traditional operations environment. Finally having something tangible to explore I started looking into Agile Operations, which led me DevOps. Lurking in the shadows for a while, I digested as much as I could of the DevOps movement. I thought it was  time to talk to some of the developers and get them on board. 6 months on and here we are... "

Devops is still a new topic for lots of people, and this introduction is a nice place to start. It provides a bit of the history, along with explaining Devops with a focus on culture, automation, measurement and sharing.

DevOps: A culture where people, regardless of title or background, work together to imagine, develop, deploy and operate a system.

DevOps is evolving from what started as little more than a rally cry, into a culture for continuous delivery of IT services. As more pieces of the puzzle fall into place, we understand that DevOps is primarily a matter of human collaboration -- assisted, but not encompassed by, certain tools and technologies. This essay is my take on DevOps, and why I think it is about embracing distributed, autonomous operational methods that support scalable human-computer processes.

A path to DevOps When Lara Hogan asked Bridget Kroumhout (on stage, at Velocity), "So, how did you get tricked into operations?" it was funny, but it got Kroumhout thinking. It's a question she's been asked before, and has sometimes been at a loss for an answer since she didn't follow a plan originally. Kroumhout now offers a plan-a wonderfully thoughtful and pragmatic set of resources beginning with culture (e.g., if you work in tech for even a little while, you'll notice that you have a lot of social and economic privilege, no matter your demographic identity, because you have more choices in your work and life than do many of your fellow humans), tools, education, community, and how to launch your career. Even if you're already well established, this is worth a read if only to rekindle your fire.

A good set of four values to help drive a devops flavoured transformation. Work lean, embrace failure, automate everything and demand diversity.

I've been interviewing candidates for a DevOps opening that Interactive Intelligence has available and I keep getting asked by candidates, 'What does DevOps mean to you?' If you were to google 'What is devops?' you'll find pages and pages of blogs and articles answering just that. I've read a few of them but I still find myself struggling to give a clear answer. I think the trouble with anwering this question is that people generally expect a 2-3 sentence answer and it's difficult to encapsulate all my thoughts on the subject that concisely. Another issue is that when I'm talking about DevOps, I feel like my attempts at explaining it come off as if it's some magical, fundamental, paradigm shift that exploded onto the scene and if followed will lead to peace on earth and an end to all hunger.

A recent study of Dev and Ops professionals in large enterprises found that those with the least mature DevOps implementations were seeing the most success. While that sounds like a paradox, it's the approach the teams took that matters.

How can there be a DevOps engineer? I often see vacancies with the job title DevOps engineer and always think, this makes no sense. DevOps is all about collaboration between two different expertises. In this blog post, I want to share the history of DevOps and my thought about the role of DevOps engineer.

DevOps cannot be a single role. What do you think?

One of the tenets of devops is sharing. But how do you best facilitate sharing in your own organisation? This essay and talk go into detail about the importance of communication, tips for asking questions and other good advice.

Discover tools and frameworks in the DevOps landscape. There are new awesome tools and frameworks being released everyday. This is an open and transparent attempt at aggregating all those. The entire source code and list of tools can be found at github.com/devopsbookmarks, and you are encouraged to contribute anything you come across. Pick tags to start exploring!

DevOps is going mainstream as large, complex organizations credit DevOps with IT transformation. Author and DevOps guru Gene Kim details how leaders have successfully transformed enterprise IT.

Nice writeup of one organisations adoption of devops ideas, in particular to help improve the quality and maintainability of deployed software.