Our Favorite 5: Security, Dealing with Culture Shock, and the State of Agile

DevOps is based on collaboration, connectivity, and the ability to get along. Should be simple, right? Yet many businesses struggle with defining the true meaning of DevOps, and the culture change that comes with an implementation. Organizations find themselves in a bigger mess than where they started. There are a lot of opinions and research on DevOps best practices and trends.  To narrow down your search, we put together our favorite five DevOps posts that sparked some interest and conversations around the VIP water cooler this week.

 

DevOps and Your Security Team

DevOps is continuing to making waves in the technology world. While many organizations struggle to overcome the shift in corporate culture, there’s one department is left in the dark more often than not: security.

 

Over the past decade, we have noticed the rapidly growing importance of cybersecurity. All too often, we see organizations at risk for major attacks. It is very important that you make an effort to keep your security teams in the loop while implementing DevOps.

 

In a recent Medium article titled, “What security experts need to know about DevOps and continuous delivery,” James Wickett breaks down three of the new development terms to show the possible implications each may have on security.

  • DevOps – With a high focus on management and monitoring, DevOps installation is the perfect time for security professionals to examine software and tools for possible leaks. Combining security procedures with operations creates a smoother workflow and creates visibility across the enterprise.
  • Continuous Delivery – The nature of continuous delivery allows security teams to quickly push a fix or solution to a problem instead of waiting to discover, diagnose, approve, and fix.
  • Build Pipelines –This final check before deployment is the perfect place for security testing. Use this last step to run attack tools, check code base changes, and run network or system audits.

 

Check out the rest of Wickett’s article here for more tips to integrate security into your DevOps solution.

 

Become a DevOps Master

DevOps may be all the rage right now, but what does it really mean to be a DevOps master? Adam Bertram breaks down the nine tips to being a DevOps master in his CIO article, “9 Hidden Talents of DevOps Ninjas.” Here are my top 5:

  • Be lazy. Bertram recommends only touching a project or code once. Spend the time to do it right the first time.
  • Accept change. Change is inevitable, especially in the world of tech. Rolling with the changes makes it easier to handle the hurdles of DevOps.
  • Be a team player. Ask questions, support team members, and be involved in your team members. As Bertram says, “DevOps is a team sport.”
  • Being open about your work helps your team move forward and measure successes or failures.
  • Never say “it’s not my job.” Job responsibilities are shared in DevOps. What once belonged to ops now belongs to everyone.

 

Combining these skills creates a person who’s flexible, easy to work with, willing to help, and able to handle all aspects of the job. In short, they epitomize the DevOps movement. Check out the Bertram’s full article here!

 

Easing Culture Shock

Building the processes and technology to change business services won’t do a thing unless there’s a culture change to support it. DevOps needs everyone on board, ready and willing to follow the new policies to make those ideas into business outcomes. But how do you make this happen?

 

HPE’s Paul Hodgett admits in his latest post on HPE’s Business Insights that it won’t be easy. Cultures are built over time, created in siloes and honed by daily repetition. Breaking down those siloes to create an open workflow among employees takes time and consideration. He recommends defining your goals, assessing the organization, encouraging people to get onboard to be successful.

 

It may not be easy, and definitely won’t be quick, but the turnaround is worth it. “For nearly 800 publicly traded organizations, high performers had close to 50 percent higher market capitalization growth over three years,” making the cultural change worth the battle. Read the rest of Hodgett’s article here.

 

The Don’ts of DevOps

On the surface, DevOps appears to be a fairly simple process: break down the silos and share the responsibilities to create communication between teams and improve both product and IT. This isn’t always the case. Computer Weekly’s recent article, “The Five Pitfalls to Avoid When Doing DevOps” shares how to handle the major bumps in the road when the current workplace culture revolts against the changes. Here are their five don’ts of implementing DevOps:

  1. Don’t see it solely as an automation activity.
  2. Don’t have a weak case for DevOps. Define your goals, business objectives and implementation plan.
  3. Don’t forget to involve compliance and audit teams. DevOps isn’t just for developers and operations – it’s for the entire organization.
  4. Don’t take a prescriptive blueprint and be rigid.
  5. Don’t oversell the concept. DevOps is not the silver bullet to answer all organizational problems.

 

Check out the full article here!

 

How to Create a DevOps Environment on a Budget

It’s a part of human nature to look for the best deal: from clipping coupons to checking prices, we all want to get the best bang for our buck, especially on the necessities. The same mentality stretches to the business world and DevOps implementation.

 

DevOps is crucial for many enterprises, but when many departments are on tight budgets, finding the right implementation and monitoring tools can be difficult. In his Devops.com post, “DevOps Stack on a Shoestring Budget,” Thomas Theakanath researches the best core DevOps tools for companies on a budget.

 

He suggests considering the factors of each application before selecting. Will it integrate with your other applications? Is your team familiar with it? Do you want to pay only subscription charges (licensed software), or would you rather customize each open source application (raising the cost)? Regardless of your budget or business goals, there’s a way to build the ideal DevOps environment for you without spending a fortune. Read the full article here for more tips!

 

Under the surface, DevOps requires thought, skill and careful planning to implement smoothly into any organization. What do you think?

Leave a Reply

You must be logged in to post a comment.