devops starts today…with you

DevOps is not a title or a team, it’s an execution pattern. It’s a method for how you work and interact with others. DevOps has an incredibly loose definition that tends to include just about anything that makes business more efficient. I believe that’s because DevOps is actually the pattern by which all these other tools, processes, and interactions are executed.

There’s an underlying mechanism which facilitates our actions. DevOps is one execution pattern for that mechanism. This pattern includes transparency of thought, inclusivity, acceptance, pursuit of excellence, innovation, efficiency of process, and continual improvement. This list should not be meant to exclude other attributes I may have missed.

What this means to you is that you are empowered to implement a DevOps execution pattern. If your company or team isn’t willing to go on this journey with you, then you can embark on it yourself. I’m certain you have some ability to control your own actions, therefore you should be able to accomplish this task. It will require you to take action and lead.

The first step is identifying what is under your control or isn’t under someone else’s control. This could be something as simple as reading about other innovators, finding the fastest way to effectively clean your whiteboard, creating a simple dashboard for JIRA or by aggregating data from Jenkins, or streamlining a form your customers use. But it could also be something more complex. It’s often easy to start with something small that provides a lot of value back.

You may even decide that your most effective contribution is writing blog posts, organizing tech talks or Meetups, creating forums for others to share knowledge, or getting your team together regularly to share with each other. Or perhaps you will choose to start meeting with your counterparts on the other side of the wall. These will all satisfy the attribute of transparency of thought.

I have found those on the other side of the wall to be quite generous and interesting. I have learned a tremendous amount from my discussions with them. This may be the single best thing you can do to start small. If you don’t know who operates your software or supports your infrastructure, then that’s your fault. It’s time to fix that.

I’m continuing my journey by writing this blog post. I will also commit to meeting regularly with my counterparts on the other side of the wall and creating more efficient ways for my team to view information about our applications. The thing about DevOps is that it’s a journey of discovery and personal transformation which never ends.