Agile Development 2.0 Deprecation: Get the Facts Before It Impacts You

[Oliver Stammler]

If you’ve been working with ServiceNow, odds are you rely on Agile Development 2.0 apps and plugins or you’ve worked closely with teams that do. This isn’t just "another product update." The upcoming deprecation of Agile Development 2.0 is going to be felt across nearly every organization using the platform, making it a massive shift for our community.

Why this matters for all/most of us

Let’s be real: Agile Development has been a core part of digital transformation and ServiceNow development for years. Most teams, from product owners to admins to developers and Scrum Masters, have built processes and integrations around these tools.

That’s why ServiceNow’s decision to deprecate Agile Development 2.0 and associated plugins in new instances (starting with the Australia AI Platform release in May 2026) is a game-changer.

While these features will stick around for existing installations for now, official support is ending once your subscription term is up. Eventually, by August 2030, Agile Development 2.0 (to be technically correct: com.snc.sdlc.agile.2.0) will be fully deprecated.

Everyone needs to take action

Now is the time for every team, admin, and developer to investigate their dependencies and start the transition conversation. While August 2030 sounds like it's still plenty of time your or your customers next renewal might be right around the corner!

What should you do?

• Check your platform: Find out where Agile Development 2.0 apps and plugins are being used in your processes and integrations.

• Get familiar with CWM: ServiceNow’s Collaborative Work Management (CWM) solution is the path forward. As of the Zürich Pricing Guidelines, it’s only available as a paid subscription, so understanding capabilities and licensing options is critical.

• Start the learning curve: Don’t wait! Start exploring CWM now, so you’re not caught off guard when you need to migrate.

• Talk to your teams: Everyone in your organization (not just ServiceNow admins!) should be aware of the upcoming change and the impact it might have.

• Treat as custom code: If you decide to keep using these plugins and apps, be aware that they’ll become “custom code”. This means you’ll be responsible for maintenance.

Additional information

Here are some initial additional information I did find and which I want to share: 

• ServiceNow Knowledge Base Article with guidance on replacement options: KB2752774 (Deprecation of Agile Development 2.0 and Migration to Collaborative Work Management (CWM)...

• ServiceNow Community Article CWM & EAP: Agile Planning and Execution at All Levels

• ServiceNow Community Article Team-level agile planning in CWM

• And of course all related ServiceNow University content

[Marcel Hopp]

I think an important point to this topic is mentioned in Deprecation of Agile Development 2.0 and Migration to Collaborative Work Management (CWM) and EAP - ...:

• At the end of your subscription term end date
  The applications and plugins listed below will reach end of support.
  • They will remain active in your instance, including during upgrades
  • ServiceNow will no longer provide support, fixes, or enhancements

From my point of view the decision of customers will therefore depend mostly on the licensing offer they get for CWM and EAP.

If the price is too high, they will probably still using Agile Development 2.0 without suport, even after their current subscription term has ended.

[Oliver Stammler]

Hey @Marcel Hopp ,

I totally agree with you.
Agile Development 2.0 is a very stable and mature product. Some customers will certainly continue to use it as custom code if the barrier to switching to CWM is too high.

[AdrianL]

Will the rm_feature table survive and continue to be used in CWM ?

[Oliver Stammler]

Hi @AdrianL ,

rm_feature is part of the Release Management v2 common plugin (com.snc.release_management_v2_common).
This plugin is not listed as deprecated within the Knowledeg Article KB2752774. Therefore I would assume that you can still use this table by installing the said plugin.

Please note that I am not part of ServiceNow and therefore I cannot guarantee you what will happen 🙂

[Mansor2]

Hello Oliver,

We have been using agile 2.0 ourselves, pretty good.  The question is,  can we have it activated for another customer who is in need of it end of this month? they have been using ServiceNow for years wihtout using Agile 2.0. 

Regards

Mansor

[Chris Chambers1]

I cant find any info about the licensing implications. Agile is a $0 SKU and therefore free for customers to use, namely to manage their ServiceNow implementation development and related work through stories etc.

CWM seems to be a paid-for feature. How will new customers be expected to manage this now? Do they need to go buy Jira/ADO licenses? Feels like a backward step unless ServiceNow are allowing CWM to be used for free.

[Oliver Stammler]

Hey @Mansor2 ,
please note that I am not part of ServiceNow and especially not part of the account team of this customer so that I cannot give any binding advice at this point.
All I can say is that for most of the customers agile development needs to be part of their order form so that they are eligable to activate the corresponding plugins. If so, they can still activate the plugins while they are on Zurich. 
This means that they should check their order form or reach out to their individual ServiceNow Account Executive to clarify.

Hope that helps!

Cheers
Oli

[Oliver Stammler]

Hey @Chris Chambers1,

that’s exactly how I see it right now. Agile was for free and CWM is a paid subscription as of now.
To be honest, though, I’m not sure to what extent this has already been finalized by ServiceNow.

I’d recommend discussing this topic in the SNUG and/or reaching out to your ServiceNow Account Executive to get more information.
Feel free to share your insights afterwards 😊