This article is based on reporting originally published on devops.com in January 2020.
A Major Merger Accelerates DevOps Consolidation
The announced merger of XebiaLabs and CollabNet VersionOne marked a significant moment in the DevOps tooling landscape, accelerating a consolidation trend that had been building for nearly two years. The combined company was to be led by Ashok Reddy, a veteran of Broadcom, CA Technologies, and IBM. XebiaLabs CEO Derek Langone was set to become president of the merged entity, while CollabNet VersionOne CEO Flint Brenton announced his departure.
Background: How the Two Companies Got Here
The merger brought together two companies with distinct but complementary histories:
- CollabNet VersionOne had been championing value stream management since its 2017 merger with VersionOne, an application lifecycle management (ALM) provider built around version control software. In late 2019, private equity firm TPG Capital acquired CollabNet VersionOne and pledged $500 million to fuel both organic and inorganic growth. TPG made the leadership appointment of Reddy as CEO of the combined entity.
- XebiaLabs raised $100 million in capital in early 2018 to invest in building out a continuous delivery (CD) platform capable of serving large enterprises.
The stated goal of the merger was to tightly integrate the two platforms and deliver enterprise-grade value stream management to Global 5,000 organizations — a segment Langone argued was underserved.
“There is no enterprise-class player in this space.”
Derek Langone, President of the combined XebiaLabs / CollabNet VersionOne entity
Langone’s view was that rival offerings either lacked the scale to serve large enterprises or were too shallow in capability to meet real business requirements.
What Is Value Stream Management?
Value stream management (VSM) is, in practice, roughly analogous to business intelligence software — but applied to the software delivery pipeline. VSM tools aggregate metrics and data from application development platforms, allowing business and engineering leaders to:
- Identify bottlenecks and delays across the software delivery lifecycle
- Quantify the business impact of those delays
- Align development work with broader business objectives
- Improve flow efficiency from idea to production
The discipline draws heavily from Lean manufacturing principles, where a “value stream” maps all steps required to deliver a product to a customer and highlights waste in the process. Applied to software, this means tracing the journey of a feature or fix from initial commit through testing, security scanning, staging, and release.
“Value stream management these days is everywhere.”
Bob Davis, Chief Marketing Officer, Plutora
How Competitors Were Responding
CloudBees: Software Delivery Management
CloudBees had already introduced value stream management modules as an extension of its CI/CD platform. At the time of the merger announcement, CloudBees CEO Sacha Labourey was positioning the company’s next step as building a Software Delivery Management (SDM) platform — a layer that normalizes data from multiple sources, including the open source Jenkins CI/CD platform and the Electric Cloud application release platform CloudBees had acquired. VSM would be one of several applications available within that broader SDM offering.
“The destination is now clear.”
Sacha Labourey, CEO, CloudBees
Labourey also predicted that M&A activity among DevOps vendors would accelerate as organizations adopted more complex architectures — particularly microservices-based systems — which increase the coordination complexity that VSM tools are designed to address.
GitLab: A Single, Unified Code Base
GitLab took a different approach. Rather than assembling capabilities through acquisitions, GitLab announced plans to build VSM capabilities natively into its platform on a single, common code base. Senior Product Manager Jackie Meshell described the market moving quickly toward the integrated model GitLab was already pursuing.
“We’re seeing the market follow that fast.”
Jackie Meshell, Senior Product Manager, GitLab
Multi-Platform Specialists
A distinct category of vendors focused on VSM tools that span multiple development platforms — avoiding vendor lock-in. Companies like Plutora, Tasktop, and Panaya were competing in this space. Bob Davis of Plutora pointed out that few enterprises are standardized on a single application development platform, making cross-platform VSM capabilities strategically important for adoption.
Why Consolidation Was Inevitable
The consolidation dynamic in DevOps tooling follows a pattern familiar in enterprise software: as a market matures and buyer expectations rise, point solutions get absorbed into platforms, and platforms compete for the role of a single pane of glass across the delivery lifecycle. Several forces were driving this in DevOps:
- Tool sprawl fatigue: Engineering teams were maintaining dozens of loosely integrated tools, each generating siloed data.
- Business alignment pressure: Executives wanted to connect software delivery metrics to business outcomes, not just technical KPIs.
- Microservices complexity: Distributed architectures increased the number of moving parts in a release, raising demand for orchestration and visibility tools.
- Private equity interest: PE firms like TPG saw consolidation plays as a way to build defensible enterprise software businesses.
The Open Question: Enterprise Timing Risk
One strategic risk highlighted in the original reporting deserves attention: a strategy focused heavily on large, slower-moving enterprise IT organizations carries timing risk. More agile competitors — often digital-native companies — continue to take market share from incumbents across industries. There is a scenario in which enterprise IT organizations finally reach the maturity level needed to adopt VSM tooling at scale only after the window of competitive relevance for those tools has shifted.
That said, wider adoption of value stream management — whether as a standalone category or as a feature set within broader SDM platforms — appeared to be a matter of when and how, not if.
Key Takeaways for DevOps Practitioners
- Value stream management is evolving from a niche practice into a mainstream enterprise requirement.
- The DevOps tooling market was consolidating around platform plays that combine CI/CD, release orchestration, and VSM.
- Vendors were pursuing three broad strategies: M&A-driven platform assembly (XebiaLabs/CollabNet), organic unified-platform development (GitLab), and cross-platform VSM specialization (Plutora, Tasktop).
- Enterprises evaluating VSM tooling should assess whether they need a platform deeply integrated with a single toolchain or one that bridges multiple existing toolchains.
- The leadership and ownership changes in merged entities (especially PE-backed ones) can affect product roadmap continuity — factor this into long-term toolchain decisions.