Articles

Hand holding black rotary telephone When DevOps Gets Lost in Translation

The waterfall method of developing software is a bunch of translation activities: The design is a translation of the requirements into the language of architecture, the code is another, and a formal test process is a third. And with each translation, there’s the opportunity to introduce error. When your DevOps team is isolated, it creates another handoff, and another point of failure.

Matthew Heusser's picture Matthew Heusser
Four people on a crew team rowing together Rowing in the Same Direction: Use Value Streams to Align Work

Ambiguity abounds about value streams, so it’s good to clarify what they are, why they matter, and how to exploit them. It's important to help employees understand the organization's definition of value, to provide visibility on how business value is created, and to focus on the fast flow of value through the value streams. If everyone understands which direction to row the boat, they can steer toward it together.

Dominica DeGrandis's picture Dominica DeGrandis
Icon showing an automated system Why You Need to Be Doing Continuous Integration

It’s usually easy and inexpensive to set up a continuous integration environment for either an agile or a waterfall project. Perhaps the most obvious benefit of CI is the elimination of the integration phase that existed in traditional waterfall projects, where we typically slip the worst on deadlines. But there are many other benefits to continuous integration that you may not have considered.

David Bernstein's picture David Bernstein
Image of lock over code DevSecOps: Incorporate Security into DevOps to Reduce Software Risk

DevSecOps is a growing movement to incorporate security into DevOps practices in order to ensure flaws and weaknesses are exposed early on through monitoring, assessment, and analysis, so remediation can be implemented far earlier than traditional efforts. By failing fast with security testing, organizations reduce risk of a security incident and decrease the cost of rework.

Alan Crouch's picture Alan Crouch
Cloud with tools graphic Fixing a Broken Deployment Process

When you have hundreds of applications performing various functions across several environments, it's tough to push all the code when it needs to be. Here are some steps to help your own team develop the internal tooling it requires to deploy thousands of applications if needed, all in a reliable, efficient manner.

Colleen Stock's picture Colleen Stock
Development, operations, and QA DevOps: Collaboration with a Purpose

Development, operations, and QA have long recognized the importance of coexistence, but they've still had weak or unbalanced relationships. DevOps emphasizes collaboration, rejecting the "us versus them" mentality. Every department needs information, feedback, and support from every other department, helping everyone see how they enable each other.

Douglas Fink's picture Douglas Fink
DevOps You Can’t Buy DevOps

There are organizations that want to “buy DevOps,” like it is a plugin to add to the development process. They often create a new role, team, department, or infrastructure. But you can't buy DevOps, and it's not a designated team, either. It is the idea of people working together. Here are some approaches to get you there.

Matt Heusser's picture Matt Heusser
implementing gears Getting Employees On Board when Implementing Change Management

Change is a difficult but important part of business. It can be most difficult on the employees, but if you involve them in the planning process and make an effort to understand their points of view, you can mitigate resistance and facilitate the experience for everyone. This article deals specifically with ERP implementation, but its advice is useful for any change management situation.

RK Prasad's picture RK Prasad
start, continue, and stop doing signs When Postmortems Meet Retrospectives: Improving Your Agile Process

If you want secure, reliable systems, you need all stakeholders actively communicating. This means involving both IT operations and developers in discussions after deployments, to ascertain if anything went wrong and can be avoided, and what went well or could be refined. Integrating your postmortems and retrospectives facilitates collaboration and improves processes.

Bob Aiello's picture Bob Aiello
two arrows merging 5 Steps to Successful Process Management in Mergers and Acquisitions

When going through a merger or acquisition, capturing the critical processes of both parties is a key to success. Including everyone in the planning helps ease the impacts of change and develop ideas for the future. Here are five steps to assist with process management and create a new organization that is greater than the sum of its parts.

Ivan Seselj's picture Ivan Seselj

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.