Site Search
Where does testing fit in a DevOps world? DevOps encourages the development and operations teams to work together.
It seems that everyone is aflutter with DevOps, the shiny new panacea for all of our software ailments. What technical goodness can DevOps bestow upon us? What riddles does it unlock for us as technologists?
The telecom industry changes rapidly, the competition is fierce, and user experience is the utmost priority. In today's world of digitization and data personalization, effective use of agility and DevOps is the key behind ensuring customer satisfaction.
Adam Auerbach, head of testing at EPAM Systems, discusses testing in DevOps and why it’s important we instill a testing culture in DevOps organizations. He says DevOps is about enabling teams to do things on their own, and he gives recommendations for some general metrics that teams can start with to measure speed and efficiency.
The ability of DevSecOps to produce secure code requires the merging of two very different cultures: AppSec and DevOps.
Many organizations are either talking about DevOps or already working toward its adoption. Books and conferences around DevOps abound, and it seems that DevOps engineers are in high demand. What impact does adopting DevOps have on a company and its people? What does DevOps look like from...
Software security often evokes negative feelings among software developers because it is associated with additional programming effort, uncertainty, and road-blocking activity on a fast release cycle. Secure software developers must follow a number of guidelines that, while intended to...
DevOps can be characterized as the assembly line of building, testing, deploying, and updating enterprise applications. Many software development organizations may claim a comprehensive DevOps strategy, but Chris Riley believes that the only way to be successful is to use a DevOps framework.
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.
DevOps is represented by a set of principles and practices that help improve communication and collaboration between development and operations. Bob Aiello and Leslie Sachs have put together a great introduction showing how quality assurance needs to commence at the very start of a DevOps project.
Achieving continuous testing is a daunting task for many test teams still struggling with combining agile, test automation, and increased speed. We know that change is rarely easy. Fixing or getting rid of some practices is tough. However, one-step-at-a-time change can take you far and fast.
For any continuously improving organization, certain actions are commonly applicable when going through large amounts of change. Dan Barker walks through the five steps to transformational change that he's found to be crucial for moving to DevOps processes.
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.
Many professionals, while having expertise in their technical niche, are sometimes less than perfect at communicating effectively with colleagues from other departments. This can result in departments failing to work effectively together; these departments resemble silos more than a collaborative and cohesive organization. This article will help you identify and understand some of the reasons why teams operate in silos and what you can do to change that.
In large financial institutions, treasury departments-specialized teams of traders and experts in liquidity, risk, accounting, financial forecasting, and quantitative analysis-manage the organization’s wealth and financial risk. These departments require large, complex, third-party software products that must change often to support the treasury’s complicated business processes.