<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IT Service Management &#8211; Best DevOps</title>
	<atom:link href="https://www.bestdevops.com/tag/it-service-management/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.bestdevops.com</link>
	<description>Lets Learn, Do it &#38; Share! Thats a Best DevOps!!!</description>
	<lastBuildDate>Wed, 14 Oct 2026 03:37:11 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.3</generator>
	<item>
		<title>IT Service Desk Software: Key Platforms, Market Segments, and Global Landscape</title>
		<link>https://www.bestdevops.com/it-service-desk-market-pdf-has-huge-demand-worldwide-profiling-global-players-samanage-freshservice-manageengine-servicedesk-jira-service-desk/</link>
					<comments>https://www.bestdevops.com/it-service-desk-market-pdf-has-huge-demand-worldwide-profiling-global-players-samanage-freshservice-manageengine-servicedesk-jira-service-desk/#respond</comments>
		
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Tue, 25 Feb 2020 05:29:07 +0000</pubDate>
				<category><![CDATA[JIRA]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[IT Service Management]]></category>
		<category><![CDATA[IT support]]></category>
		<category><![CDATA[Jira]]></category>
		<category><![CDATA[Software-Market]]></category>
		<guid isPermaLink="false">http://www.bestdevops.com/?p=10854</guid>

					<description><![CDATA[A practical overview of the IT service desk software market, covering leading platforms such as Freshservice, ManageEngine ServiceDesk, Jira Service Management, and ServiceNow, along with deployment models, key use cases, and the competitive dynamics shaping the sector.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">The IT service desk software market is one of the more competitive segments within enterprise IT tooling. Organizations of every size—from mid-market companies to global enterprises—depend on service desk platforms to manage incidents, service requests, change workflows, and end-user support. This article provides a practical overview of the major platforms, deployment options, primary use cases, and the competitive dynamics that define this space.</p>



<h2 class="wp-block-heading">What Is an IT Service Desk Platform?</h2>



<p class="wp-block-paragraph">An IT service desk platform—sometimes called an ITSM (IT Service Management) tool—provides a centralized system for logging, routing, tracking, and resolving IT issues. Beyond basic ticketing, modern platforms typically include:</p>



<ul class="wp-block-list">
  <li>Incident and problem management</li>
  <li>Service request catalogues</li>
  <li>Change and release management workflows</li>
  <li>Asset and configuration management databases (CMDB)</li>
  <li>Self-service portals and knowledge bases</li>
  <li>SLA tracking and reporting dashboards</li>
  <li>Automation and AI-assisted triage</li>
</ul>



<p class="wp-block-paragraph">Many platforms now offer integrations with DevOps toolchains, cloud monitoring systems, and communication tools such as Slack and Microsoft Teams, blurring the line between traditional ITSM and modern DevOps workflows.</p>



<h2 class="wp-block-heading">Major IT Service Desk Platforms</h2>



<p class="wp-block-paragraph">The following platforms are among the most widely evaluated and deployed across enterprise and mid-market environments. Each has a distinct positioning, pricing model, and feature emphasis.</p>



<h3 class="wp-block-heading">Freshservice (Freshworks)</h3>



<p class="wp-block-paragraph">Freshservice targets mid-market and growing enterprise teams with a clean UI, fast deployment, and ITIL-aligned workflows out of the box. It includes a native asset management module, an AI assistant (Freddy AI), and strong automation capabilities. Freshservice is cloud-native and integrates with a wide range of third-party tools.</p>



<h3 class="wp-block-heading">ManageEngine ServiceDesk Plus</h3>



<p class="wp-block-paragraph">ManageEngine ServiceDesk Plus is a long-standing ITSM platform from Zoho Corp that offers both cloud-hosted and on-premises deployment. It supports full ITIL process coverage including incident, problem, change, release, and project management. Its on-premises option makes it attractive for organizations in regulated industries with strict data-residency requirements.</p>



<h3 class="wp-block-heading">Jira Service Management (Atlassian)</h3>



<p class="wp-block-paragraph">Formerly called Jira Service Desk, Jira Service Management is tightly integrated with the broader Atlassian ecosystem (Jira Software, Confluence, Bitbucket). It is particularly popular in software development organizations because it bridges developer and operations workflows naturally. Teams already using Jira Software for agile project management can extend service management to IT ops and DevOps pipelines with minimal friction.</p>



<h3 class="wp-block-heading">ServiceNow</h3>



<p class="wp-block-paragraph">ServiceNow is the dominant platform in large enterprise ITSM. It offers an extensive suite of modules covering IT workflows, HR service delivery, customer service management, and security operations. ServiceNow&#8217;s depth comes with significant implementation complexity and licensing cost, making it best suited for organizations with dedicated ITSM administrators and the need for highly customized workflows.</p>



<h3 class="wp-block-heading">Zendesk</h3>



<p class="wp-block-paragraph">While Zendesk originated as a customer support platform, many IT teams use it as a lightweight service desk. Its strengths lie in ease of use, multi-channel support (email, chat, phone, social), and reporting. It is generally more suited to internal IT helpdesk use cases than to full ITIL process management.</p>



<h3 class="wp-block-heading">BMC Helix (formerly BMC Remedy)</h3>



<p class="wp-block-paragraph">BMC Remedy has been a fixture in enterprise ITSM for decades. The platform has evolved into BMC Helix, a cloud-native SaaS offering with AI-driven automation, predictive service management, and strong CMDB capabilities. Like ServiceNow, it is primarily aimed at large enterprises with complex operational requirements.</p>



<h3 class="wp-block-heading">Cherwell IT Service Management</h3>



<p class="wp-block-paragraph">Cherwell (now part of Ivanti following an acquisition) was known for its no-code/low-code customization model, allowing ITSM administrators to build and modify workflows without writing code. It offered both cloud and on-premises deployment and had a loyal mid-market customer base.</p>



<h3 class="wp-block-heading">Spiceworks</h3>



<p class="wp-block-paragraph">Spiceworks is a free, ad-supported help desk platform popular with small IT teams and MSPs. It offers basic ticketing, network monitoring, and an active community forum. While it lacks the enterprise-grade features of ServiceNow or ManageEngine, its zero-licensing-cost model makes it a practical entry point for small organizations.</p>



<h3 class="wp-block-heading">Agiloft</h3>



<p class="wp-block-paragraph">Agiloft positions itself on extreme configurability without custom coding. It covers ITSM workflows as well as contract lifecycle management, making it a versatile option for organizations looking to consolidate tooling.</p>



<h3 class="wp-block-heading">SolarWinds Web Help Desk / Track-It!</h3>



<p class="wp-block-paragraph">Track-It! is a veteran help desk and asset management tool aimed at small to mid-sized IT departments. SolarWinds also offers Web Help Desk as a separate product. Both are on-premises-first solutions with straightforward ticketing and asset tracking.</p>



<h3 class="wp-block-heading">EasyVista</h3>



<p class="wp-block-paragraph">EasyVista provides ITSM and enterprise service management capabilities with a focus on European markets, particularly France. It offers both cloud and on-premises deployment and covers ITIL v4 processes.</p>



<h3 class="wp-block-heading">GoTo Resolve (formerly GoToAssist)</h3>



<p class="wp-block-paragraph">GoToAssist—now rebranded as GoTo Resolve—combines remote support tooling with lightweight ticketing. It is primarily positioned as a remote access and support solution rather than a full-featured ITSM platform.</p>



<h2 class="wp-block-heading">Deployment Models</h2>



<p class="wp-block-paragraph">IT service desk platforms are generally available in two primary deployment models, each with distinct trade-offs:</p>



<h3 class="wp-block-heading">Cloud-Based (SaaS)</h3>



<ul class="wp-block-list">
  <li><strong>Faster time to value:</strong> No infrastructure provisioning required; teams can be productive within days.</li>
  <li><strong>Automatic updates:</strong> The vendor manages upgrades, patches, and scaling.</li>
  <li><strong>Subscription pricing:</strong> Costs are predictable and tied to agent or user count.</li>
  <li><strong>Data residency considerations:</strong> Organizations in regulated industries must verify where data is stored and processed.</li>
</ul>



<h3 class="wp-block-heading">On-Premises</h3>



<ul class="wp-block-list">
  <li><strong>Full data control:</strong> Data never leaves the organization&#8217;s own infrastructure.</li>
  <li><strong>Customization depth:</strong> More access to underlying configuration and integrations.</li>
  <li><strong>Higher operational overhead:</strong> The organization is responsible for patching, backups, and scaling.</li>
  <li><strong>Suitable for air-gapped environments:</strong> Government, defense, and certain healthcare deployments may require fully isolated systems.</li>
</ul>



<h2 class="wp-block-heading">Primary Use Cases and Industry Verticals</h2>



<p class="wp-block-paragraph">IT service desk platforms are deployed across a broad range of industries and use cases. The most common include:</p>



<ul class="wp-block-list">
  <li><strong>IT support teams:</strong> The core use case—managing incidents, service requests, and change workflows for internal IT departments.</li>
  <li><strong>Healthcare:</strong> Hospitals and healthcare networks use ITSM platforms to manage clinical IT systems, device support, and compliance workflows under HIPAA requirements.</li>
  <li><strong>Education:</strong> Universities and school districts use service desks to support faculty, staff, and student IT requests, often with high seasonal demand spikes.</li>
  <li><strong>Financial services:</strong> Banks and insurance companies rely on ITSM platforms for change management and audit trails required by regulatory frameworks.</li>
  <li><strong>Managed Service Providers (MSPs):</strong> MSPs use multi-tenant service desk platforms to manage support across many client accounts simultaneously.</li>
</ul>



<h2 class="wp-block-heading">Competitive Dynamics</h2>



<p class="wp-block-paragraph">The IT service desk market is notably fragmented. At the enterprise tier, ServiceNow and BMC Helix compete for large accounts, while Jira Service Management has made significant inroads in technology companies. The mid-market is contested by Freshservice, ManageEngine ServiceDesk Plus, and Cherwell/Ivanti. The SMB segment is largely served by Spiceworks, Zoho Desk, and lower-tier tiers of the mid-market platforms.</p>



<p class="wp-block-paragraph">Key competitive vectors include:</p>



<ul class="wp-block-list">
  <li><strong>AI and automation:</strong> Vendors are investing heavily in AI-powered ticket classification, virtual agents, and predictive incident management.</li>
  <li><strong>DevOps integration:</strong> Platforms that integrate cleanly with CI/CD pipelines, monitoring tools, and alert management systems are increasingly preferred in software-driven organizations.</li>
  <li><strong>Low-code workflow configuration:</strong> The ability for ITSM administrators to build custom workflows without developer involvement is a significant differentiator.</li>
  <li><strong>Total cost of ownership:</strong> Licensing, implementation, and ongoing administration costs vary dramatically between vendors and strongly influence platform selection.</li>
  <li><strong>Mobile experience:</strong> Support for mobile-first IT technicians and end users is now table stakes rather than a premium feature.</li>
</ul>



<h2 class="wp-block-heading">Regional Market Presence</h2>



<p class="wp-block-paragraph">Adoption patterns and dominant vendors vary by region:</p>



<ul class="wp-block-list">
  <li><strong>North America (US, Canada, Mexico):</strong> The largest market by revenue. ServiceNow, Jira Service Management, and Freshservice have strong North American customer bases.</li>
  <li><strong>Europe (Germany, UK, France, Italy):</strong> Strong adoption of both global platforms and regional players such as EasyVista. GDPR compliance is a critical evaluation criterion.</li>
  <li><strong>Asia-Pacific (China, Japan, India, South Korea):</strong> Rapid growth driven by digital transformation initiatives. ManageEngine has significant adoption in India given Zoho&#8217;s origin. Local cloud data residency requirements shape vendor selection.</li>
  <li><strong>Middle East and Africa:</strong> Growing adoption among government and telecommunications organizations, with cloud data sovereignty being a key concern.</li>
  <li><strong>South America (Brazil, Argentina, Chile):</strong> Growing market with increasing SaaS adoption, though on-premises deployments remain more common than in North America and Western Europe.</li>
</ul>



<h2 class="wp-block-heading">Key Evaluation Criteria When Selecting a Platform</h2>



<p class="wp-block-paragraph">When comparing IT service desk platforms, engineering and IT operations teams should evaluate the following:</p>



<ol class="wp-block-list">
  <li><strong>ITIL alignment:</strong> Does the platform support the ITSM processes your organization actually uses (incident, change, problem, asset management)?</li>
  <li><strong>Integration ecosystem:</strong> Can it connect to your monitoring stack (Datadog, PagerDuty, Prometheus), communication tools (Slack, Teams), and existing DevOps toolchain?</li>
  <li><strong>Scalability:</strong> Will the platform handle your ticket volume and agent count at your expected growth trajectory without a significant price jump?</li>
  <li><strong>Deployment model:</strong> Does the vendor&#8217;s cloud offering meet your data residency and compliance requirements, or do you need on-premises?</li>
  <li><strong>Self-service capability:</strong> How capable is the end-user portal and knowledge base in deflecting tickets before they reach an agent?</li>
  <li><strong>Reporting and analytics:</strong> Does the platform provide the SLA reporting, trend analysis, and exportability your leadership team requires?</li>
  <li><strong>Total cost of ownership:</strong> Factor in licensing, professional services for implementation, training, and ongoing administration effort.</li>
</ol>



<h2 class="wp-block-heading">Summary</h2>



<p class="wp-block-paragraph">The IT service desk platform market offers options for every organization size, budget, and technical requirement. Cloud-native platforms like Freshservice and Jira Service Management have lowered the barrier to deploying ITIL-aligned workflows, while enterprise platforms like ServiceNow and BMC Helix continue to dominate complex, large-scale deployments. The right choice depends on your team&#8217;s size, existing toolchain, compliance obligations, and willingness to invest in implementation and ongoing administration. A structured evaluation—including proof-of-concept testing with your actual ticket workflows—remains the most reliable path to selecting the right platform.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bestdevops.com/it-service-desk-market-pdf-has-huge-demand-worldwide-profiling-global-players-samanage-freshservice-manageengine-servicedesk-jira-service-desk/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>IT Service Management (ITSM) Software: Market Overview and Key Vendors (2019–2026)</title>
		<link>https://www.bestdevops.com/it-service-management-itsm-software-market-2019-strategic-assessment-servicenow-atlassian-ivanti-heat-software-ibm-ca-technologies/</link>
					<comments>https://www.bestdevops.com/it-service-management-itsm-software-market-2019-strategic-assessment-servicenow-atlassian-ivanti-heat-software-ibm-ca-technologies/#respond</comments>
		
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Fri, 12 Jul 2019 06:13:10 +0000</pubDate>
				<category><![CDATA[IT Training]]></category>
		<category><![CDATA[IT Service Management]]></category>
		<category><![CDATA[Micro Focus]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[Software Market]]></category>
		<guid isPermaLink="false">http://www.bestdevops.com/?p=6117</guid>

					<description><![CDATA[An overview of the ITSM software market landscape, covering leading vendors such as ServiceNow, Atlassian, Ivanti, IBM, and BMC Software, along with deployment models, market segments, and regional growth drivers.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><strong>Note:</strong> This article is based on a market summary originally sourced from financialplanning24.com (published July 2019). Specific market size figures and CAGR projections are drawn from that third-party report and have not been independently verified by this publication.</p>



<h2 class="wp-block-heading">What Is ITSM Software?</h2>



<p class="wp-block-paragraph">IT Service Management (ITSM) software provides organizations with structured frameworks and tooling to plan, deliver, manage, and improve IT services. Rooted in methodologies such as ITIL (IT Infrastructure Library), ITSM platforms typically cover incident management, problem management, change management, service catalog, asset management, and self-service portals. Both enterprise IT departments and managed service providers rely on ITSM tools to align technology services with business needs and to meet service-level agreements (SLAs).</p>



<h2 class="wp-block-heading">Key Vendors in the Global ITSM Software Market</h2>



<p class="wp-block-paragraph">The ITSM market is served by a broad range of vendors, from large enterprise platform providers to focused mid-market specialists. Prominent companies active in this space as of 2019 include:</p>



<ul class="wp-block-list">
<li><strong>ServiceNow</strong> – widely regarded as the market leader for enterprise ITSM and broader IT operations management (ITOM).</li>
<li><strong>Atlassian</strong> – known for Jira Service Management (formerly Jira Service Desk), popular with DevOps and software engineering teams.</li>
<li><strong>Ivanti (formerly HEAT Software)</strong> – offers ITSM alongside unified endpoint management capabilities.</li>
<li><strong>IBM</strong> – provides ITSM through its Watson AIOps and Maximo/Control Desk portfolios targeting large enterprises.</li>
<li><strong>CA Technologies (now part of Broadcom)</strong> – delivered ITSM as part of its broader IT management suite.</li>
<li><strong>BMC Software</strong> – competes directly with ServiceNow via its Helix and Remedy platforms.</li>
<li><strong>Cherwell Software</strong> – known for its codeless configuration model aimed at mid-market organizations.</li>
<li><strong>Freshworks (Freshservice)</strong> – a cloud-native, SaaS-first option popular with SMEs and growing enterprises.</li>
<li><strong>SolarWinds Service Desk</strong> – targets IT teams seeking affordable, easy-to-deploy ITSM.</li>
<li><strong>SysAid</strong> – an established mid-market player with strong automation features.</li>
<li><strong>SAP</strong> – integrates ITSM capabilities within its broader enterprise application ecosystem.</li>
<li><strong>Micro Focus (formerly HPE)</strong> – offers ITSM via its Service Manager product line.</li>
<li><strong>TOPdesk, Samanage, Agiloft, Axios Systems, ASG Software, Ultimo, Epicor, Symantec, Autotask</strong> – additional vendors covering specialized verticals or regional markets.</li>
</ul>



<h2 class="wp-block-heading">Deployment Models</h2>



<p class="wp-block-paragraph">ITSM software is available in several deployment configurations, each suited to different organizational requirements:</p>



<ul class="wp-block-list">
<li><strong>Cloud-based (SaaS)</strong> – Hosted and maintained by the vendor. Lower upfront cost, rapid deployment, and automatic upgrades make this the dominant growth model. ServiceNow, Freshservice, and Jira Service Management all lead with SaaS-first approaches.</li>
<li><strong>On-premises</strong> – Software installed within the organization&#8217;s own data center. Preferred by regulated industries (finance, healthcare, government) with strict data residency or compliance requirements.</li>
<li><strong>Hybrid</strong> – A combination of cloud and on-premises components, often used during cloud migration transitions.</li>
</ul>



<h2 class="wp-block-heading">Market Segments by Organization Size</h2>



<p class="wp-block-paragraph">ITSM solutions are adopted across organizations of all sizes, though the feature requirements and budget constraints differ significantly:</p>



<ul class="wp-block-list">
<li><strong>Small and Medium Enterprises (SMEs)</strong> – Typically prioritize ease of use, quick deployment, and cost efficiency. Vendors such as Freshservice, SolarWinds Service Desk, and SysAid are common choices in this segment.</li>
<li><strong>Large Enterprises</strong> – Require deep customization, enterprise integrations, advanced analytics, and multi-site support. ServiceNow, BMC Helix, and IBM solutions dominate at this scale.</li>
</ul>



<h2 class="wp-block-heading">Regional Market Landscape</h2>



<p class="wp-block-paragraph">The ITSM software market has a global footprint, with adoption driven by digital transformation initiatives across multiple regions:</p>



<ul class="wp-block-list">
<li><strong>North America</strong> (United States, Canada, Mexico) – The largest regional market, driven by early technology adoption, a large base of enterprise IT organizations, and mature DevOps practices.</li>
<li><strong>Europe</strong> (Germany, France, UK, Italy, Russia, and others) – A significant and growing market. The EU region was cited in the source report as representing approximately USD 538 million in 2017, with a projected CAGR of around 10.5% through 2026.</li>
<li><strong>Asia-Pacific</strong> (China, India, Japan, South Korea, Australia, and others) – Rapid IT investment growth, particularly in India and China, is driving strong ITSM adoption.</li>
<li><strong>Central &amp; South America</strong> (Brazil and others) – An emerging market with growing enterprise IT adoption.</li>
<li><strong>Middle East &amp; Africa</strong> (GCC countries, Turkey, Egypt, South Africa, and others) – Increasing investment in digital infrastructure is spurring ITSM adoption across the region.</li>
</ul>



<h2 class="wp-block-heading">Key Market Drivers and Challenges</h2>



<h3 class="wp-block-heading">Drivers</h3>



<ul class="wp-block-list">
<li><strong>Cloud adoption</strong> – Migration to cloud infrastructure creates demand for cloud-native ITSM tools that integrate with modern DevOps pipelines.</li>
<li><strong>Digital transformation</strong> – Organizations modernizing business processes rely on ITSM frameworks to manage service delivery at scale.</li>
<li><strong>AI and automation</strong> – Vendors are embedding machine learning for predictive incident management, automated ticket routing, and virtual agents, reducing manual workload on IT teams.</li>
<li><strong>Remote and distributed work</strong> – Growing reliance on digital services increases the volume and complexity of IT support needs.</li>
<li><strong>Regulatory compliance</strong> – Industries such as finance and healthcare require documented, auditable IT change processes, reinforcing ITSM adoption.</li>
</ul>



<h3 class="wp-block-heading">Challenges</h3>



<ul class="wp-block-list">
<li><strong>Implementation complexity</strong> – Enterprise ITSM platforms can require lengthy, expensive rollouts and significant customization effort.</li>
<li><strong>Vendor lock-in</strong> – Deep platform customization can make future migrations costly.</li>
<li><strong>Adoption and change management</strong> – Technical tools alone do not guarantee service improvement; organizational buy-in and process discipline are essential.</li>
<li><strong>Integration with DevOps toolchains</strong> – Bridging traditional ITSM workflows with agile/DevOps practices (sometimes called DevOps or ESM) remains an ongoing challenge.</li>
</ul>



<h2 class="wp-block-heading">ITSM and DevOps: A Growing Intersection</h2>



<p class="wp-block-paragraph">For DevOps engineering teams, ITSM is increasingly relevant beyond traditional IT operations. Change management workflows, incident response runbooks, and service catalog automation all intersect with CI/CD pipelines and site reliability engineering (SRE) practices. Platforms such as Jira Service Management are explicitly designed to bridge the gap between development teams and IT operations, enabling shared on-call schedules, linked deployments, and unified incident timelines. Evaluating ITSM tooling through a DevOps lens—looking at API integrations, webhook support, and infrastructure-as-code compatibility—has become a standard part of platform selection.</p>



<h2 class="wp-block-heading">Summary</h2>



<p class="wp-block-paragraph">The ITSM software market encompasses a wide range of vendors and deployment models, serving organizations from SMEs to global enterprises. Cloud-based delivery continues to displace on-premises installations, while AI-driven automation is reshaping how incidents and service requests are handled. For DevOps and platform engineering teams, choosing an ITSM platform that integrates natively with modern development toolchains is as important as its core ITIL compliance. The competitive landscape—led by ServiceNow, BMC, Atlassian, and Freshworks—continues to evolve rapidly, with consolidation (such as CA Technologies&#8217; acquisition by Broadcom) reshaping vendor options.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bestdevops.com/it-service-management-itsm-software-market-2019-strategic-assessment-servicenow-atlassian-ivanti-heat-software-ibm-ca-technologies/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>DevOps Trend Fueled by IT&#8217;s Need for Speed: What the Survey Data Shows</title>
		<link>https://www.bestdevops.com/robust-devops-trend-fueled-by-its-need-for-speed-survey-says/</link>
					<comments>https://www.bestdevops.com/robust-devops-trend-fueled-by-its-need-for-speed-survey-says/#respond</comments>
		
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Wed, 09 Aug 2017 08:35:32 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[IT trends]]></category>
		<category><![CDATA[DevOps Trend]]></category>
		<category><![CDATA[global IT Service]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[IT Service Management]]></category>
		<category><![CDATA[Robust DevOps trend]]></category>
		<category><![CDATA[Survey]]></category>
		<guid isPermaLink="false">http://www.bestdevops.com/?p=2372</guid>

					<description><![CDATA[Survey data from Pink Elephant's ITSM conference reveals that speed-to-market has overtaken process maturity as the top IT priority, accelerating DevOps adoption across organizations.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><em>This article is based on survey analysis originally published on TechTarget, drawing on research conducted by Troy DuMoulin, VP of Research and Development at Pink Elephant, a global IT Service Management (ITSM) training and consulting firm.</em></p>



<h2 class="wp-block-heading">Why This DevOps Wave Is Different</h2>



<p class="wp-block-paragraph">DevOps is not the first large-scale IT improvement initiative to gain industry momentum — but according to Troy DuMoulin of Pink Elephant, it may be the most durable. Writing on TechTarget, DuMoulin argues that previous IT transformation efforts were largely driven by internal innovation cycles. The current DevOps push, by contrast, is propelled by external economic and competitive forces: digital disruption has made speed-to-market a survival requirement rather than a nice-to-have.</p>



<p class="wp-block-paragraph">Pink Elephant surveyed attendees at its annual ITSM conference to test whether these observations matched real organizational priorities. The results across several questions paint a consistent picture: IT teams are consciously trading process maturity for velocity, and they are reaching for frameworks — DevOps, Lean, and Agile — that promise exactly that.</p>



<h2 class="wp-block-heading">DevOps-Focused Transformation: Where Organizations Stand</h2>



<p class="wp-block-paragraph">The survey&#8217;s first question asked respondents whether they were actively working on a DevOps-focused transformation. The intent was to measure how broadly the term <em>DevOps culture</em> had been adopted as a label for organizational improvement goals — specifically, the dismantling of silos and the improvement of cross-team communication and collaboration.</p>



<p class="wp-block-paragraph"><strong>Finding:</strong> A majority of respondents — 57% — indicated that transforming to a DevOps culture was a current, active focus of their organization. While the question was binary and does not capture the depth or maturity of those efforts, the result suggests that DevOps has moved well beyond early-adopter status and into mainstream IT planning.</p>



<figure class="wp-block-image"><img decoding="async" src="http://cdn.ttgtmedia.com/rms/onlineImages/cio-devops_transforming_culture_desktop.jpg" alt="Survey result: Are you actively transforming your organization to a DevOps culture?" /></figure>



<h2 class="wp-block-heading">Speed Over Maturity: A Significant Shift in Priorities</h2>



<p class="wp-block-paragraph">Pink Elephant has run its annual conference for more than three decades. Historically, attendee discussions centered on ITSM process maturity, control frameworks, and high-availability practices. Over the three years prior to this survey, however, DuMoulin observed a marked shift in the language used by conference participants: terms associated with control and stability gave way to terms associated with urgency, velocity, and speed-to-market.</p>



<p class="wp-block-paragraph">To test whether this language shift reflected genuine organizational priorities, the survey asked directly: <em>Is process speed currently more important than process maturity?</em></p>



<p class="wp-block-paragraph"><strong>Finding:</strong> Close to 60% of surveyed organizations confirmed that speed is currently more important to them than process maturity. This is a striking result from an audience historically focused on ITIL-aligned process rigor. It suggests that competitive pressure — not internal preference — is driving organizations to accept higher process risk in exchange for faster delivery cycles.</p>



<figure class="wp-block-image"><img decoding="async" src="http://cdn.ttgtmedia.com/rms/onlineImages/cio-devops_process_speed_maturity_desktop.jpg" alt="Survey result: Is process speed more important than process maturity this year?" /></figure>



<h2 class="wp-block-heading">Frameworks Identified with Velocity: Year-Over-Year Adoption Trends</h2>



<p class="wp-block-paragraph">To understand which frameworks organizations are investing in, the survey asked respondents to select all methodologies currently representing an area of focus. The question was kept identical across two consecutive survey years to allow direct comparison. Respondents could choose multiple frameworks, and the results reflect current investment priorities rather than a ranking of overall importance.</p>



<figure class="wp-block-image"><img decoding="async" src="http://cdn.ttgtmedia.com/rms/onlineImages/cio-devops_area_of_focus_desktop.jpg" alt="Survey result: What frameworks or methodologies are currently areas of focus?" /></figure>



<p class="wp-block-paragraph">The year-over-year comparison surfaces three notable trends:</p>



<ul class="wp-block-list">
<li><strong>Waterfall project management declined sharply.</strong> Investment in traditional sequential, activity-based project management fell by 66% compared to the previous year&#8217;s survey. Waterfall remains a primary method in most organizations, but active development investment in the approach is dropping quickly.</li>
<li><strong>DevOps adoption grew 7% year over year.</strong> This was the highest positive change of any velocity-focused framework in the comparison period.</li>
<li><strong>Lean IT grew 6% year over year.</strong> Lean&#8217;s emphasis on eliminating waste and improving flow aligns directly with the speed-to-market priorities respondents identified elsewhere in the survey.</li>
</ul>



<p class="wp-block-paragraph">Agile also registered strong overall adoption — second only to ITSM across all frameworks listed. Given that ITSM adoption is expected given the conference context, Agile&#8217;s position reinforces the broader pattern: organizations are systematically reallocating attention toward frameworks that promise faster value delivery.</p>



<figure class="wp-block-image"><img decoding="async" src="http://cdn.ttgtmedia.com/rms/onlineImages/cio-devops_changes_year_desktop.jpg" alt="Year-over-year framework adoption changes (2016–2017)" /></figure>



<h2 class="wp-block-heading">The Call to Action: Digital Disruption Leaves No Room for Delay</h2>



<p class="wp-block-paragraph">DuMoulin draws a historical parallel to make the scale of this shift concrete. The current IT transformation, he argues, is comparable in impact to the transition from centralized mainframe computing to decentralized client-server architectures. The critical difference is the driver: the client-server revolution was sparked by internal IT innovation, whereas the current transformation is being forced by external economic and competitive conditions.</p>



<p class="wp-block-paragraph">Digital disruptors — competitors who have built software-first business models — can move faster, iterate more cheaply, and reach customers more directly than traditional enterprises. Organizations that do not increase their own speed to market risk losing market position to these competitors. In this context, the rapid growth of the DevOps trend is not a fad. It is a rational organizational response to an existential competitive threat.</p>



<p class="wp-block-paragraph">The survey data supports this conclusion: organizations are not adopting DevOps because it is fashionable. They are adopting it — along with Lean and Agile — because they have concluded that their current delivery speeds are incompatible with the competitive environment they face.</p>



<h2 class="wp-block-heading">Key Takeaways for DevOps Practitioners</h2>



<ul class="wp-block-list">
<li><strong>DevOps adoption is majority-level:</strong> More than half of surveyed IT organizations are actively pursuing a DevOps cultural transformation, not just evaluating it.</li>
<li><strong>Speed has displaced maturity as the top priority:</strong> Nearly 60% of organizations now rate delivery speed above process maturity — a significant change for an audience historically focused on ITIL rigor.</li>
<li><strong>Waterfall is losing investment, not just mindshare:</strong> A 66% year-over-year decline in active investment in waterfall project management represents a concrete reallocation of organizational attention.</li>
<li><strong>Lean and DevOps are growing together:</strong> The parallel growth of Lean IT and DevOps reflects a shared underlying goal: eliminating friction and accelerating the flow of value from idea to production.</li>
<li><strong>External pressure is the primary driver:</strong> Unlike previous IT transformation waves, the current DevOps push is being driven by competitive necessity rather than internal IT advocacy.</li>
</ul>



<p class="wp-block-paragraph"><em>Original analysis by Troy DuMoulin, Pink Elephant. Source: TechTarget.</em></p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bestdevops.com/robust-devops-trend-fueled-by-its-need-for-speed-survey-says/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Hiscox CTO: DevOps Is About Survival, Not Just Speed</title>
		<link>https://www.bestdevops.com/hiscox-cto-emphasises-devops-is-about-survival/</link>
					<comments>https://www.bestdevops.com/hiscox-cto-emphasises-devops-is-about-survival/#respond</comments>
		
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Mon, 31 Jul 2017 15:54:16 +0000</pubDate>
				<category><![CDATA[IT Training]]></category>
		<category><![CDATA[CTO Emphasises]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Hiscox]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[IT Service Management]]></category>
		<category><![CDATA[Microsoft Azure]]></category>
		<guid isPermaLink="false">http://www.bestdevops.com/?p=2287</guid>

					<description><![CDATA[Hiscox CTO Jonathan Fletcher explains how a cloud-first strategy accelerated the insurer's end-to-end DevOps transformation—and why he believes DevOps is now a matter of business survival.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><em>This article is based on an interview originally published on <a href="https://www.infoq.com" rel="noopener">InfoQ</a>, covering Jonathan Fletcher&#8217;s talk at the DevOps Enterprise Summit London in June 2017.</em></p>



<h2 class="wp-block-heading">Cloud Migration as a DevOps Catalyst</h2>



<p class="wp-block-paragraph">Hiscox CTO Jonathan Fletcher used his talk at the DevOps Enterprise Summit (DOES) London 2017—titled <em>&#8220;Sorry Mr(s) Ops, We Hadn&#8217;t Forgotten You – Part Two of the Hiscox Story&#8221;</em>—to argue that DevOps is no longer a nice-to-have: it is a matter of business survival. Building on his 2016 DOES talk, Fletcher detailed how moving to a cloud-first strategy became the forcing function that pushed Hiscox toward a genuinely end-to-end DevOps model, one that finally brought operations teams into the picture alongside development.</p>



<h2 class="wp-block-heading">Early Wins—and a Blind Spot in Operations</h2>



<p class="wp-block-paragraph">Fletcher was candid about a pattern familiar to many enterprises: early DevOps gains concentrated entirely inside development teams while operations remained in a traditional, siloed role. Hiscox&#8217;s development-side improvements were significant:</p>



<ul class="wp-block-list">
  <li>Number of people involved in a release reduced from <strong>eight to two</strong></li>
  <li>Deploy frequency increased from <strong>two per week to fifty per day</strong></li>
  <li>Deployment time cut from <strong>four hours to twenty minutes</strong></li>
</ul>



<p class="wp-block-paragraph">Despite these results, IT operations had been largely overlooked. The continuous delivery pipeline existed within the development boundary. Recognising this blind spot led the team to ask how DevOps principles could be extended to ops—and that question pointed toward cloud adoption as a structural answer.</p>



<h2 class="wp-block-heading">Choosing Azure and Embracing &#8220;Move Fast, Fix Later&#8221;</h2>



<p class="wp-block-paragraph">Hiscox selected Microsoft Azure as its cloud platform, a decision Fletcher attributed to the company&#8217;s existing investment in Microsoft technologies, combined with the observation that AWS and Azure were the clear market leaders at the time. Neither vendor was technically disqualified; the decision was ultimately driven by reducing switching costs and leveraging existing organisational familiarity.</p>



<p class="wp-block-paragraph">Fletcher acknowledged an initial preference for re-architecting applications before moving them to the cloud—the instinct to avoid a &#8220;lift and shift&#8221; approach without exploiting cloud-native benefits. That position evolved pragmatically: Hiscox shifted to a strategy of moving as quickly as possible and refactoring afterward. The target set at the time of the talk was for three of Hiscox&#8217;s largest systems—collectively transacting hundreds of millions of pounds of business—to go live in Azure by the end of 2017.</p>



<h2 class="wp-block-heading">The 2020 Vision: IT as Strategic Advantage</h2>



<p class="wp-block-paragraph">Fletcher outlined a longer-term ambition: by 2020, Hiscox aimed for IT to be a source of strategic, competitive differentiation rather than what he called a &#8220;subservient order taker.&#8221; The financial model underpinning this was also evolving—rather than building and owning infrastructure, the goal was to rent IT services (SaaS and cloud platforms), allowing expense costs to flatten even as the business grew.</p>



<h2 class="wp-block-heading">Q&#038;A with Jonathan Fletcher: Key Themes from DOES London 2017</h2>



<p class="wp-block-paragraph">InfoQ spoke with Fletcher in more detail following his talk. The following exchanges cover the practical and cultural dimensions of Hiscox&#8217;s DevOps journey.</p>



<h3 class="wp-block-heading">On the &#8220;IT-Less IT Team&#8221; Concept</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>InfoQ:</strong> The audience loved the &#8216;IT-Less IT Team&#8217; phrase—what are the steps needed to get there?</p>
<p><strong>Fletcher:</strong> From an IT point-of-view it&#8217;s about aligning tools, processes and ideas in IT and getting on a common platform. Then getting deeper integration with the business and federating IT out to the business—then removing IT as an entity and embedding IT skills into the business&#8217;s value streams. At Hiscox there is a group budget for IT that, with cloud, we are pushing back into the business as a discretionary spend.</p>
<p>The move to cloud and consuming things rather than building them will also make this happen naturally. Using SaaS and doing due diligence to ensure it&#8217;s the right product is a different skill set from designing and building it ourselves. It will reduce our IT touch points.</p>
</blockquote>



<p class="wp-block-paragraph">Fletcher also made a broader cultural observation: as digital literacy becomes universal across generations, the concept of a discrete &#8220;IT department&#8221; becomes increasingly anachronistic. IT skills will simply be part of what competent business professionals possess.</p>



<h3 class="wp-block-heading">On Breaking the &#8220;Not My Job&#8221; Anti-Pattern</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>InfoQ:</strong> You highlighted &#8216;not my job&#8217; as a classic DevOps anti-pattern. What&#8217;s the strategy for changing that behaviour?</p>
<p><strong>Fletcher:</strong> It&#8217;s a cultural thing—we need to be focused on being a single team and all share the attitude that it&#8217;s everyone&#8217;s responsibility to get it over the line. Silos create handoffs. The Agile Manifesto helps with this in that the basis of it is that we are not individual parts but part of a greater team.</p>
</blockquote>



<h3 class="wp-block-heading">On the Connection Between Cloud-First and DevOps</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>InfoQ:</strong> You say that cloud-first is accelerating the DevOps revolution—what is the connection?</p>
<p><strong>Fletcher:</strong> You can do cloud without doing DevOps, but whether you <em>should</em> is the question. You are potentially just moving the problem. What moving to cloud gives you is more time to tackle the way you deliver and make improvements around speed, quality, security and performance.</p>
</blockquote>



<p class="wp-block-paragraph">This is an important nuance. Cloud adoption is an enabler, not a substitute, for organisational and cultural DevOps practice. Organisations that migrate infrastructure without changing their delivery model simply replicate on-premises dysfunction in a different environment.</p>



<h3 class="wp-block-heading">On DevOps as Competitive Advantage</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>InfoQ:</strong> You say DevOps is critical for businesses stealing a march on their competition. Why?</p>
<p><strong>Fletcher:</strong> It&#8217;s around the changing role of IT. IT used to be a subservient order taker from the business but it&#8217;s becoming a two-way conversation. We need to ask questions like: if a process that took eight hours only takes twenty seconds, what does that mean for the business? Insurance in particular is about understanding risk, which is essentially a data problem; if we can understand the data problem we can serve our customers better.</p>
</blockquote>



<h3 class="wp-block-heading">On Why DevOps So Often Stays in Development</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>InfoQ:</strong> Many organisations at DOES face the challenge of DevOps being done in dev only, with ops left behind. Why does this happen and how can it be remedied?</p>
<p><strong>Fletcher:</strong> The focus on dev happens because there is more obvious value in changing the development cycle—businesses want to get more change out of the door. The theory of continuous delivery gets people excited about change velocity, as does the appetite for Agile, which also came from a software engineering perspective. We need to take the ops teams on the same journey: help them move away from waterfall, get to automation, use lean tools and Value Stream Mapping. It&#8217;s the same approach—but it&#8217;s a bigger jump for ops, as they are unfamiliar with these ways of working. Things that help are training, cross-skilling, mentoring and coaching—giving them the skills to just get on and do it.</p>
</blockquote>



<h3 class="wp-block-heading">On the ITSM vs. ALM Tension</h3>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p><strong>InfoQ:</strong> What was the most valuable insight for you from DOES this year?</p>
<p><strong>Fletcher:</strong> ITSM versus ALM is the big one for me—it&#8217;s driving lots of conversation about how to tackle the technology and process problem where these two worlds are so unfamiliar to each other. Who wants to write a user story when they raise a support ticket?</p>
</blockquote>



<p class="wp-block-paragraph">The ITSM (IT Service Management) versus ALM (Application Lifecycle Management) divide remains one of the most persistent friction points for organisations trying to achieve true DevOps integration. Development teams operate around stories, sprints and backlogs; operations teams work with incidents, changes and service requests. Bridging that tooling and process gap is as much a cultural challenge as a technical one.</p>



<h2 class="wp-block-heading">Key Takeaways for DevOps Practitioners</h2>



<ul class="wp-block-list">
  <li><strong>DevOps without ops is incomplete.</strong> Early delivery-pipeline wins are valuable but leave organisations exposed if operations teams are not brought into the transformation.</li>
  <li><strong>Cloud enables but does not replace DevOps culture.</strong> Moving to the cloud without addressing organisational silos relocates, rather than resolves, the underlying problems.</li>
  <li><strong>&#8220;Move fast, fix later&#8221; can be pragmatic.</strong> A phased migration—lift and shift first, re-architect later—may be the only realistic path for large enterprises with time-sensitive transformation goals.</li>
  <li><strong>The ITSM/ALM gap is real and largely unsolved.</strong> Organisations should invest explicitly in bridging incident-management and development workflows, not assume the tools will converge on their own.</li>
  <li><strong>IT&#8217;s role is shifting from cost centre to value creator.</strong> The longer-term argument for DevOps investment is not efficiency—it is competitive differentiation and the ability to ask fundamentally different questions of business processes.</li>
</ul>
]]></content:encoded>
					
					<wfw:commentRss>https://www.bestdevops.com/hiscox-cto-emphasises-devops-is-about-survival/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
