CA Rally Licensing Changes

CA Rally — now formally CA Agile Central, though the Rally name remains the common usage — has experienced significant licensing changes since the Broadcom acquisition. The product, originally built by Rally Software and acquired by CA Technologies in 2015, has moved through three licensing eras: the Rally Software standalone era, the CA Technologies era (2015-2018), and the Broadcom era (2018-present). The 2026 customer experience differs from each of the preceding eras in important ways. This article sets out exactly what has changed in CA Rally licensing under Broadcom, what the current model looks like in 2026, and how customers should approach renewals and displacement decisions.

The CA Rally licensing model in 2026

Rally is licensed by named user under three principal edition tiers. The metric — named user — has been consistent across all three ownership eras, but the edition structure and per-user pricing have evolved significantly under Broadcom.

Edition structure

The Rally edition tiers in 2026 are:

• Team edition: covers core agile project management at the team level, including iteration planning, backlog management, basic reporting, and standard integrations. Suitable for individual scrum or kanban teams operating relatively independently.
• Programme edition: adds programme-level features including programme increment (PI) planning, dependency mapping, advanced portfolio visualisation, and additional integrations. Suitable for organisations running scaled agile frameworks at the programme level.
• Enterprise edition: adds enterprise-scale features including advanced portfolio management, strategic planning integration, custom reporting, and the broadest integration set. Suitable for organisations running enterprise-scale agile across multiple programmes.

User-type structure within each edition

Each edition includes multiple user types with different per-user pricing:

• Standard users: full Rally functionality at the edition level. Highest per-user price.
• Stakeholder users: read-only access plus limited interaction. Lower per-user price, but the restriction is enforced and audited.
• Administrators: full users with administrative scope. Sometimes counted as standard users, sometimes separately.

What has changed under Broadcom

The Rally licensing changes since the Broadcom acquisition fall into five categories:

1. Per-user pricing increases

The most visible change. Per-user list pricing has approximately doubled across all edition tiers since the acquisition. Customers renewing in 2026 routinely see proposals at 1.8x to 2.2x their pre-acquisition annual per-user cost. The increases compound across renewal cycles; customers who have renewed twice since the acquisition are typically running at the top of this range.

2. Discount discretion narrowing

Field sales discount discretion on Rally has been substantially reduced. Discounts that were routinely 40-60% off list under CA Technologies are now typically 15-30% off list under Broadcom. The discount floor has moved up materially.

3. Term-length pressure

Annual Rally subscriptions are still available but priced at a 20-30% premium versus three-year commitments. Five-year commitments produce additional discount tiers. The pricing structure incentivises long-term commitment in a way that did not exist under CA Technologies.

4. Edition migration pressure

Customers on Team edition are routinely pushed toward Programme or Enterprise editions at renewal. The pitch is feature value; the financial impact is significant. Customers should resist edition migration unless they will actually use the additional features.

5. Bundle pressure

Broadcom has begun positioning Rally as part of broader DevOps and value stream management bundles, particularly with the ValueOps platform. The bundle economics depend heavily on customer use of the included components; Rally-only customers should resist bundle migration that costs more than their Rally-only renewal.

The user-counting question

Rally's named-user metric has a definition that audits frequently exploit. Broadcom's standard interpretation counts as a "user" any individual with an active Rally account, regardless of recent activity. The customer's defensible position is often narrower:

• Active users only: users who have logged in within a defined window (e.g., 90 days) should be counted; users who have not should be deactivated and not counted.
• Standard versus stakeholder classification: the user's actual role within Rally should determine the user-type classification, not the default at account creation.
• Service accounts: automated integrations that operate as Rally accounts should be excluded if the contract permits, or specifically licensed at the appropriate tier.
• External users: vendors, contractors, and external collaborators are sometimes counted as users; the customer should verify the contractual treatment.

The Rally audit risk

Rally audits are less common than other Broadcom audits but do occur, particularly in connection with renewals for larger customers. The audit findings typically focus on:

• User-count overstatement — accounts that exist but are not actively used.
• Edition feature usage — whether Programme or Enterprise features are being used by customers licensed only for Team.
• Stakeholder user usage — whether users licensed as stakeholders are actually using standard-user features.
• Integration scope — whether Rally's API integrations are properly licensed.

The defence requires careful Rally configuration documentation and active user-management. Customers who allow Rally accounts to proliferate without active cleanup are exposed at audit.

The Rally renewal model

Rally renewals under Broadcom follow the standard Broadcom playbook with Rally-specific elements. The renewal proposal typically arrives 60-90 days before the renewal date and includes the headline annual figure, the user count, the proposed edition, and any bundling moves Broadcom proposes.

Renewal preparation

Customers should approach Rally renewal with:

• Current user inventory, classified by user type and active-or-inactive status.
• Edition feature usage data: which Programme or Enterprise features are actually in use, by which users.
• Integration inventory: which Rally integrations are deployed and used.
• Growth projections: realistic user-count projections for the proposed contract term.
• Alternative evaluations: at minimum, current pricing and capability information for the principal Rally alternatives.

Renewal negotiation tactics

The negotiation levers on Rally renewal:

• User-count rationalisation: removing inactive users from the licensed count reduces the proposal value without changing per-user pricing. Routinely produces 10-25% reduction.
• Edition right-sizing: holding to the lowest edition that covers actual feature usage. Routinely produces 15-35% reduction if migration from a higher edition is feasible.
• User-type rebalancing: ensuring users are licensed at the type that matches their actual usage (stakeholder versus standard).
• Term-length optimisation: pricing both annual and multi-year options to capture the discount differential.
• Contract-term negotiation: audit clauses, price-lock provisions, and termination rights.

The displacement question for Rally

Rally has strong displacement options in 2026. The principal alternatives:

Atlassian Jira (with Advanced Roadmaps)

The leading enterprise alternative to Rally. Jira's Advanced Roadmaps (formerly Portfolio for Jira) provides programme-level and portfolio-level planning capabilities comparable to Rally's Programme and Enterprise editions. Per-user pricing is competitive. The migration from Rally to Jira is well-precedented, with multiple service providers offering migration toolkits.

Microsoft Azure DevOps Boards

Bundled into Azure DevOps subscriptions, and increasingly into Microsoft 365 licensing. The pricing economics are highly favourable for Microsoft-centric customers, particularly those already paying for Azure DevOps for source control and CI/CD. The capability gap from Rally has narrowed materially; Azure DevOps Boards now covers most enterprise agile use cases.

Linear

A newer entrant focused on engineering workflow management. Cleaner user experience than either Rally or Jira; smaller but growing enterprise customer base. Most suitable for engineering-led organisations rather than enterprise-PMO-led organisations.

ServiceNow Strategic Portfolio Management

Particularly relevant for customers already on ServiceNow for IT service management. The capability set is broader than Rally but the pricing is enterprise-tier.

The migration economics

Rally migration is operationally intensive but well-bounded. The principal cost categories:

• Migration tooling and services: $100,000-$300,000 for a typical enterprise migration to Jira or Azure DevOps. Higher for highly customised Rally environments.
• User retraining: 1-2 weeks per user team to become productive on the new platform. Typical enterprise impact: 10,000-30,000 user-hours of training and ramp-up.
• Integration re-engineering: Rally integrations into CI/CD, source control, and other systems must be rebuilt for the target platform. Typically $50,000-$150,000.
• Parallel-platform period: typically 60-120 days of running both Rally and the target platform. Modest infrastructure cost but operational overhead.

The total migration cost for a typical 5,000-user Rally enterprise is in the range of $400,000-$800,000. The break-even against continued Rally under Broadcom is usually achieved within 18-36 months, depending on the renewal price increase and the chosen target platform.

The displacement decision framework

For Rally specifically, the displacement decision framework has four questions:

1. Is the Rally renewal price acceptable? Define "acceptable" against the displacement TCO.
2. Does an alternative cover the customer's actual use cases? Not the marketed Rally capabilities, but the capabilities the customer actually uses.
3. Does the organisation have the operational capacity to absorb the migration? User retraining at enterprise scale is non-trivial.
4. Is the renewal timing compatible with a migration timeline? Rally migrations typically need 6-12 months end to end.

Customers who answer "yes" to displacement on three of these four questions usually proceed with displacement. Customers who answer "no" on two or more usually renew — though increasingly they renew on shorter terms to preserve future displacement optionality.

Common Rally renewal and audit mistakes

1. Account proliferation. Allowing Rally accounts to remain active for users who have left the organisation or moved to roles that no longer use Rally. The over-count compounds at audit.
2. Edition migration without analysis. Accepting Broadcom's edition migration proposal without explicit pricing analysis. The "feature value" framing often masks material cost increase.
3. Bundle acceptance. Accepting the ValueOps or similar bundle without component-level pricing analysis. Bundles are valuable for some customers and unfavourable for others.
4. Late displacement evaluation. Beginning the displacement evaluation inside the renewal window. The 6-12 month migration timeline requires earlier start.
5. Failing to update user classifications. Allowing users licensed as stakeholders to use standard-user features. The audit finding is straightforward.

The future trajectory

The CA Rally market position is one of the weaker areas of the broader Broadcom enterprise software portfolio. The displacement market is mature, the alternatives are strong, and customer churn has been higher than in other Broadcom product areas. Customers who plan as though Broadcom Rally pricing will continue elevating, and who maintain credible displacement capability, are well-positioned for either outcome: continued use at negotiable terms, or successful migration if Broadcom's pricing posture becomes untenable.

Final word

CA Rally licensing changes under Broadcom have been substantive: higher per-user pricing, narrower discount discretion, edition migration pressure, and increased bundle positioning. The customer impact varies. Customers with disciplined user-management and active renewal negotiation continue to receive defensible commercial outcomes, with renewal increases held to 10-20%. Customers without these disciplines routinely see 30-50% increases and accept edition migrations that compound the cost over time. The disciplines are not exotic: active user inventory management, edition-feature usage tracking, and structured renewal negotiation. The customers who do this work consistently outperform; the customers who do not, consistently overpay.

CA Rally licensing — frequently asked questions

How much price increase should we expect at our next Rally renewal?

Customers without active negotiation typically see 30-50% increases over prior contract. Customers with active negotiation and credible alternatives typically hold the increase to 10-20%. Customers committed to displacement and signalling that decision credibly sometimes negotiate flat renewals during the transition period.

Should we accept the Programme or Enterprise edition migration Broadcom is proposing?

Only if the additional features are genuinely required. Document the specific Programme or Enterprise features that the customer needs; if those features are not in active use, the edition migration is not justified by feature value, and the pricing impact (typically 30-60% increase over Team edition) is the controlling consideration.

How long does a Rally-to-Jira migration take?

For a 5,000-user enterprise, 6-9 months end to end including evaluation, pilot, production rollout, parallel operation, and Rally decommissioning. The bottleneck is usually user training and organisational change management, not the technology.

What if our Rally deployment is heavily customised?

Customisation increases migration complexity but rarely makes migration infeasible. The migration team should produce a customisation inventory early, identify the items that have target-platform equivalents, and identify the items that require manual recreation or business-process change. Heavily customised environments typically have 15-30% longer migration timelines.

Can we negotiate Broadcom Rally pricing against an active displacement evaluation?

Yes, very effectively. Customers with documented displacement evaluations — signed POC agreements with Jira or Azure DevOps, completed proof-of-concept results, written migration plans — routinely receive Rally renewal proposals 25-45% better than the initial offer. The credibility of the displacement threat matters; soft threats do not produce the same effect.