This article is based on a market overview originally sourced from Galus Australis (2020). Specific revenue figures, growth rates, and forecasts from the original third-party market report are not reproduced here, as they could not be independently verified. The analysis below reflects publicly observable trends from the period.
Background: The Pandemic as a Forcing Function for Collaboration Tools
The COVID-19 pandemic, which accelerated sharply through 2020, forced organisations worldwide to shift to remote and distributed work almost overnight. For engineering and DevOps teams accustomed to co-located standups and physical whiteboards, this created an immediate and pressing need for robust project collaboration software. The result was a rapid re-evaluation of existing toolchains and, in many cases, accelerated adoption of cloud-based platforms that could support distributed teams at scale.
Key Market Segments
Deployment Model: Cloud vs. On-Premise
Project collaboration software is broadly split into two deployment models:
- Cloud-based: Hosted SaaS solutions accessible from any location with an internet connection. The pandemic significantly boosted this segment, as organisations needed tools that employees could access from home without VPN complexity or infrastructure investment.
- On-premise: Self-hosted deployments that give organisations full control over data residency and security. Regulated industries (finance, healthcare, government) often retain on-premise deployments for compliance reasons, though the management overhead is higher.
Enterprise Size: Large Enterprises vs. SMEs
Demand patterns diverged significantly by organisation size during the pandemic:
- Large enterprises prioritised integrations with existing ITSM, ERP, and CI/CD pipelines, and frequently required SSO, advanced permissions, and audit logging.
- SMEs gravitated toward lower-cost, easy-to-onboard SaaS tools with minimal setup time, favouring products with generous free tiers or transparent per-seat pricing.
Major Players in the Project Collaboration Software Market
The market is highly fragmented, with vendors competing on workflow flexibility, integration depth, pricing, and vertical focus. Key platforms active during this period included:
| Platform | Primary Strength | Typical Audience |
|---|---|---|
| Jira (Atlassian) | Deep Agile/DevOps workflows, extensive plugin ecosystem | Engineering and DevOps teams |
| Asana | Task and project management with timeline views | Cross-functional teams, PMOs |
| Trello | Kanban-based simplicity, low barrier to entry | Small teams, visual thinkers |
| Wrike | Gantt charts, resource management, enterprise reporting | Mid-market and enterprise PMOs |
| Basecamp | Opinionated simplicity, flat pricing model | Agencies, SMEs |
| Zoho Projects | Part of the broader Zoho ecosystem, strong CRM integration | SMEs already using Zoho suite |
| Mavenlink | Professional services automation, resource planning | Consulting and services firms |
| Workfront (Adobe) | Marketing and creative workflow management | Marketing teams, agencies |
| Clarizen | Enterprise portfolio management | Large enterprises, PMOs |
| Huddle | Secure document collaboration | Government and regulated industries |
| Comindware | Business process and workflow automation | Operations-heavy organisations |
| Kanbanchi | Google Workspace-native Kanban | Google Workspace users |
Other platforms noted in the market overview include Nutcache, Projectplace, Viewpoint, Easy Projects, Deskera, Genius Project, and ZilicusPM, each targeting specific verticals or workflow models.
How the Pandemic Shifted Market Dynamics
Accelerated Cloud Migration
Organisations that had delayed cloud adoption were compelled to act quickly. Many negotiated emergency licensing or took advantage of extended free trials offered by vendors in response to the pandemic. This compressed what might have been a multi-year migration into weeks.
Integration with DevOps Pipelines
For engineering teams, standalone project tracking was not enough. The period saw heightened demand for tools with native integrations into CI/CD systems (Jenkins, GitHub Actions, GitLab CI), incident management platforms (PagerDuty, Opsgenie), and communication tools (Slack, Microsoft Teams). Jira’s deep integration with the Atlassian ecosystem (Confluence, Bitbucket, Opsgenie) gave it an advantage in DevOps-heavy organisations.
Competitive Strategy Changes
Several vendors responded to the disruption by:
- Expanding free tier limits to capture users displaced by budget freezes
- Accelerating feature development in video conferencing integrations
- Publishing security and compliance documentation to address enterprise concerns about cloud data residency
- Offering academic and non-profit pricing to support institutions under strain
Market Drivers and Restraints
Drivers
- Remote work normalisation: Even as pandemic restrictions eased, many organisations retained distributed or hybrid work models, sustaining demand for collaboration tooling.
- Agile adoption: Broader adoption of Agile and DevOps methodologies increased reliance on sprint planning, backlog management, and continuous delivery tooling.
- Global team distribution: Organisations increasingly hired across time zones, making asynchronous collaboration tools essential rather than supplementary.
Restraints and Challenges
- Tool sprawl: Rapid adoption led to fragmentation, with teams using incompatible tools across departments, creating integration headaches.
- Security concerns: Moving sensitive project data to cloud platforms raised data residency and compliance concerns, particularly in regulated sectors.
- Budget constraints: Economic uncertainty caused by the pandemic led some organisations to freeze software spending, slowing adoption in cost-sensitive segments.
- Change fatigue: Teams already under stress from remote work adaptation showed resistance to adopting new tooling simultaneously.
What DevOps Teams Should Evaluate
If you are selecting or reassessing project collaboration software for a DevOps or engineering team, the following criteria remain relevant regardless of market conditions:
- CI/CD and SCM integrations: Confirm native integrations with your source control (GitHub, GitLab, Bitbucket) and pipeline tools. Webhook support is a minimum; bidirectional sync is preferable.
- Deployment model flexibility: If data residency or air-gapped environments are a requirement, confirm the vendor offers a self-hosted or private cloud option.
- Workflow customisation: Engineering teams have specific workflow states (e.g., In Review, Blocked, Ready for QA) that generic PM tools may not support cleanly.
- Reporting and visibility: Burndown charts, cycle time, and throughput metrics should be available without exporting data to spreadsheets.
- Pricing model scalability: Per-seat pricing can become expensive quickly. Understand the cost trajectory as your team grows.
- SSO and RBAC: Enterprise teams require SAML/OIDC SSO and granular role-based access control as baseline features, not premium add-ons.
Summary
The COVID-19 pandemic did not create the project collaboration software market, but it materially accelerated its growth and shifted the competitive landscape. Cloud-based tools gained ground rapidly, vendors competed aggressively on integrations and pricing, and organisations that had deferred modernising their collaboration toolchains were forced to act. For DevOps teams, the lasting takeaway is that resilient, integration-rich, cloud-accessible collaboration infrastructure is no longer optional — it is a core operational requirement.