More than half (60 percent) of respondents in the North American ‘Business Benefits of Service Virtualization’ study conducted by CA Technologies claim that customer-facing applications are delayed as a result of endemic constraints within the software development and testing environment including limited access to infrastructure, databases and undeveloped applications.
To compound the situation, applications are often released with reduced functionality, according to 70 percent of those surveyed.
The vast majority of the 200 in-house software development executives and managers from large (US $1 Billion+) enterprises surveyed are aware of the significant consequences that result from endemic constraints across software development and testing. This includes loss of reputation (96 percent) and customers switching to competitors (93 percent).
“North American businesses are under pressure to deliver increasingly complex applications, and at a much faster rate than ever before to keep pace with customer demands,” said Shridhar Mittal, general manager, Service Virtualization, CA Technologies. “Unfortunately, IT budgets are not increasing at the rate of change inherent in today’s highly distributed composite applications. This causes serious constraints to software development, resulting in delays and failures in delivering new software features to market.”
Delays in application development and testing are negatively impacting businesses with respondents reporting reduced functionality (74 percent) and late delivery of new customer facing applications (60 percent). In part, this is due to the increased pressure and demand for highly sophisticated applications, with 66 percent of respondents stating that their approach to software development and testing will have to change as a result of massive growth particularly across mobile.
The pressures highlighted by this independent study point to the need for improved development processes and faster, more effective testing. North American survey respondents also identified the potential benefits of pursuing updated approaches to include increased quality (81 percent), faster time-to-market (76 percent) and reduced costs (71 percent).
Service Virtualization addresses these challenges by enabling teams to develop and test an application using a virtual service environment that has been configured to imitate a real production environment. This provides the ability to change the behavior and data of these virtual services easily in order to validate different scenarios.
“This research follows a European study conducted in July 2012 in which 32 percent of respondents revealed that they were expected to deliver and manage four to seven releases a year compared to 53 percent in North America,” said Ian Parkes, Managing Director, Coleman Parkes Research. “Even more surprising, 75 percent of respondents across North America and Europe reported they were seeking additional budget to pay for more application development man-hours, when we know that additional labor is not in fact the ideal solution.”
According to the study, “These survey results suggest that development managers often bring new applications or services from testing environments into production without complete insight into how their integrated applications might fail. For engineers, understanding failure modes is a critical part of the job, yet according to this study, 69 percent did not have this insight on a consistent basis. This is an alarming prospect for any board giving the green light for new software projects, especially those that impact the customer. It is also concerning that only nine percent have comprehensive insight into how complex integrated applications could break in production."
About the Study
The independent study was conducted by Coleman Parkes Research in September 2012, underwritten by CA Technologies, and includes feedback from 200 in-house software development executives and managers from large enterprises with revenues of more than US$1 billion in the US and Canada. It is the second phase of a similar July 2012 study conducted in Europe.
The Latest
Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...
In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ...
Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...
Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...
Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...
The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...
The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...
In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...
AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.
The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...