Welcome to DevOps Agenda

It’s not hyperbole to claim the DevOps movement affects every level of the IT organizational chart, and exploring it requires a new way of looking at enterprise IT.

DevOps isn’t coming, it’s already here. Nearly 40% of TechTarget’s enterprise audience has implemented DevOps for...

at least some of its projects and processes, and another 50% are interested in doing the same. Talk to any enterprise CIO, CTO or IT manager, and the story is the same: Enterprises are turning to DevOps in response to a market that demands agility, with faster release cycles, minimal mistakes, and constant uptime.

It’s not hyperbole to claim the DevOps movement affects every level of the IT org chart. Application developers, operations staff, senior management, and software testers can expect DevOps to not only upend their day-to-day operation, but also their fundamental relationship to one another, and the enterprise as a whole.

Exploring DevOps requires more than practical know-how. It requires a new way of looking at IT, focusing on individuals and connections, all while keeping an eye on the bigger picture.

And that’s why we built DevOps Agenda, the latest addition to TechTarget’s ever-growing portfolio, and a different kind of IT site. This is contributor-driven outlet, featuring input from those driving the change, from those dealing with the change, from, well, you.

DevOps is a major business disruption, with both varying and overlapping effects. For nearly 20 years, TechTarget has helped enterprise technology buyers navigate similar touchpoints, including mobile, cloud, virtualization, and BYOD, with a tried-and-true approach: a network of concentrated sites with unmatched coverage scope and breadth, featuring grounded, knowledgeable, and independent tips, strategies, and news for IT pros.

Because DevOps has a layered meaning, functionally defined by the tools and technologies that enable it, but more often suggestive of the cultural change it brings to enterprise IT shops, we are in a uniquely suited to do the same again, but this time with an added wrinkle in the form of DevOps Agenda.

For DevOps tools and technologies, sister sites SearchITOperations, SearchSoftwareQuality, and SearchMicroservices offer targeted DevOps coverage specifically concerning architecture, CI/CD, development, management, monitoring, production, releasing, testing, security, and more.

Here on DevOps Agenda, you’ll find commentary and insights. Strong and informed opinions are encouraged, and in the DevOps spirit of constructive communication, respectful disagreements always welcome.

DevOps is a big topic. We want to have a big conversation.

So please, vent, post, quibble, argue, share, support, agree, debate, challenge and concur.

And of course, welcome to DevOps Agenda.

Dig Deeper on Topics Archive

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

I am auditing DevOps. Any insights into the big issues I should be auditing? Thanks.
Just finished talking to the auditor last week.  When he audited us he wanted to confirm that the controls we had in place (example, business area approval for production migrations) was still in place, even if we were automating the actual release of the application into Production.

So what does this mean for the average team/business?  If there is a control for xxxxx.  After DevOps has taken hold of the process, the intent of the control still needs to be in place.  If it isn't then the control either isn't useful and a new control needs to be developed, the control isn't useful or there is a problem.  We took a predominantly manual process of emails, approvals and drop folders and automated the process while still maintaining the initial control:  business approval.  After confirming that the approval was indeed given and that we could trace that approval for any automated deployment done, he was happy.

A number of DevOps enthusiasts want to abandon all controls but DevOps is more about finding a way to automate, streamline and report on the success without causing additional work.