While everyone is convinced about the benefits of containers, to really know if you're making progress, you need to measure container performance using KPIs.These KPIs should shed light on how a DevOps team is faring in terms of important parameters like speed, quality, availability, and efficiency. Let's look at the specific KPIs to track for each of these broad categories ...
This is the third in a series of three blogs directed at recent EMA research on the digital war room. In this blog, we'll look at three areas that have emerged in a spotlight in and of themselves — as signs of changing times — let alone as they may impact digital war room decision making. They are the growing focus on development and agile/DevOps; the impacts of cloud; and the growing need for security and operations (SecOps) to team more effectively ...
For a few years now, it has seemed like agile developers and DevOps teams haven't been giving testing its proper due. One could almost picture them thinking, "So what if there's a bug, design flaw or performance issue. We'll fix it in the new version next week." Of course, this line of thinking has turned out to be a big mistake ...
The digital war room — physical, virtual or hybrid — is not in retreat but in fact is growing in scope to include greater participation from development and security. It's also becoming more proactive, with on average more than 30% of "major incidents" before they impacted business service performance. In this blog I'm providing a few additional highlights from the insights we got on digital war room organization and processes ...
EMA has just completed research titled, Unifying IT for Digital War Room Performance. The research was partly inspired by current debates about the role of the "War Room" and how it is or is not evolving. Some seem lost in fantasy — "the war room will absolutely disappear." Whereas for others, basic incident handling is just emerging and having a more defined and effective war room team remains a hope for the distant future ...
When it comes to smart app development, I have learned plenty of lessons over my years in technology. Here are five that are top of mind for me ...
Nine out of ten (89.1 percent) of information security leaders are concerned about the rise of digital threats they are experiencing across web, social and mobile channels, according to the 2018 CISO Survey, conducted by RiskIQ ...
Organizations are focusing investments on security and analytics, while actively researching emerging technologies such as machine learning and artificial intelligence, according to the 2018 CIO Tech Poll: Tech Priorities survey ...
Companies today face a digital dilemma. How can they understand and discern if their approach to transforming their company to meet today's digital consumer is the right one? ...
One overlooked opportunity for improving DEV and OPS collaboration is inviting database administrators (DBAs) to the DevOps conversation. DBAs function in a unique role where bridging the gap between development and operations occurs daily ...
QualiTest recently compiled a data report analyzing software testers globally. The report details the Quality Assurance and Software Testing job market, one of the fastest growing job markets and a bellwether of tech employment due to QA's involved in nearly every conceivable industry ...
The number of malware breaches (to use a generic term) are rising in near exponential numbers and, unless there are radical changes, this is set to continue unabated. Most pundits agree with this forecast ...
Organizations that are actively managing the quality of open source components flowing into production applications are realizing a 28 percent improvement in developer productivity, a 30 percent reduction in overall development costs, and a 48 percent increase in application quality, according to the 2017 State of the Software Supply Chain Report from Sonatype ...
Being able to deploy distinct code elements quickly, matched with the ability to deploy the next release version or the previous version, facilitates moving forward, even on failure. The small program unit minimizes the production impact upon failure — maybe only a few people experience the problem instead of a large set of application users when large code deployments go wrong. Besides implementing small code segments, there are two additional reasons why fail forward has proven successful: continuous integration and testing ...
Compiling, packaging, and deploying large applications at once into production are some of the major reasons for disgruntlement between development and operations. The release causes huge problems for the business and customers, with operations under the gun to find and rectify the failure — often with no development assistance. That division ends with DevOps ...
