Everything you need to understand what's changing, discover what Collaborative Work Management offers, and decide when and how to make the move — all in one place.

Rest Assured:

Your access is not going away, and there is no forced cutover date.

If you are a current Agile Development 2.0 customer, you can continue to use the application and access all of your data. There is no deadline by which you must move. We are not taking anything away. We are, however, investing heavily in CWM because we believe it delivers significantly more value — and we think you'll want to make the move when the time is right for your organization.

 

01 — What is happening with the Agile 2.0 deprecation, and when?

ServiceNow has officially begun the deprecation process for Agile Development 2.0. This means new customers can no longer get started on Agile 2.0. Here is what the timeline actually means for you.

 

• April 2026 — End of Sale for new customers. New customers can no longer purchase Agile Development 2.0 or install the Agile Development plug-in. Agile Development has also been removed from SPM SKUs.

• Sept 2026 (Planned) — End of Renewal for the Agile Teams SKU. Existing customers will not be able to renew contracts that include Agile Development. However, customers can continue to use Agile 2.0 and will not be out of compliance.

• TBD (2029+) — End of Support. This will not be reached until all active Agile Development contracts have expired. End of Support just means that the application will be treated as a customization and support cases won't be supported. Even at End of Support, you retain full access to your data and functionality. The application will not be deactivated.

 

Bottom line: You can continue to use Agile Development 2.0. There is no hard cutoff date. That said, Agile 2.0 is built on a legacy tech stack and will see no new feature development. CWM is where all future investment is going — with new capabilities releasing monthly.

 

Agile Development 2.0 Deprecation KB — https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2752774

 

 

02 — What is CWM?

Collaborative Work Management (CWM) is ServiceNow's modern, integrated workspace for knowledge workers — giving teams a single hub to plan, visualize, and collaborate on any type of work. It is not simply Agile 3.0. CWM is an entirely different product and agile planning is just one capability.

CWM brings together work that previously lived in disconnected tools — incidents, stories, tasks, demands, goals, and more — into a single pane of glass. Teams can work in List, Gantt, Kanban, or Sprint Planning views, collaborate on documents in real time, create automations, align work to strategic goals, and benefit from Now Assist AI capabilities. 

 

When combined with Strategic Portfolio Management, work in CWM can be aligned to enterprise-wide planning and governance. CWM can be aligned to strategic goals, included in portfolio plans, and connecting to scaled agile planning in Enterprise Agile Planning. 

 

 

What CWM includes that Agile 2.0 does not

• Collaborative Docs — real-time document collaboration with Now Assist AI support

• My Work Dashboard — a single view of all work across CWM boards, projects, stories, and RIDAC tasks

• Custom Columns & Automations — custom fields, formulas, and automations, all created by end-users

• Multiple Views — List, Gantt, Kanban, and Sprint Planning views

• Connected Work — replaces Unified Backlog but brings in the actual work items 

• Strategic Alignment — align work to SPM goals, portfolios, and Enterprise Agile Planning

• Now Assist (AI) — task generation, summarization, and more

• Time Card — time tracking included at no additonal cost.

Licensing note:  CWM is included in the SPM license and available as a standalone license. 

 

Getting Started Resources

• CWM Overview Video (YouTube) — https://www.youtube.com/watch?v=g--00jLY_M8
   A brief introduction to Collaborative Work Management and what it can do for your team
• Quick Guide to CWM Implementation — https://www.servicenow.com/community/cwm-articles/quick-guide-to-cwm-implementation/ta-p/2914658
   Step-by-step getting-started guidance for setting up CWM in your organization

03 — Find your path: Team-Level Agile vs. Team of Teams

Not everyone needs the same solution. The right fit depends on whether your teams are planning independently or coordinating across multiple teams. Use the guide below to find your path.

 

CWM Only — Team-Level Agile Planning

Best for: Individual agile teams managing their own sprints, backlogs, and stories — not coordinating across ARTs or multiple scrum teams.

• Sprint planning & backlog management

• Stories, epics, and scrum tasks

• Cross-type dependencies

• Connected Work (replaces Unified Backlog)

• List, Gantt, Kanban, and Sprint Planning views

• Custom columns, automations, and docs

Learn more about team-level agile planning in CWM — https://www.servicenow.com/community/cwm-articles/team-level-agile-planning-in-cwm/ta-p/3486281

 

CWM + EAP — Team of Teams (Scaled Agile)

Best for: Organizations running Agile Release Trains, SAFe, or Scrum of Scrums — where multiple teams coordinate through a shared program increment.

• All CWM team-level capabilities

• PI Planning with Enterprise Agile Planning (EAP)

• Features, capabilities, and epics across teams

• Scrum Programs (ART-level)

• Cross-team dependency management

• Shared data model between CWM and EAP — progress flows seamlessly between the two

Learn more about CWM & EAP: Agile Planning and Execution at All Levels:

•   https://www.servicenow.com/community/cwm-articles/cwm-amp-eap-agile-planning-and-execution-at-all-levels/ta-p/3338062
• Unified Agile: CWM + EAP Demo Video (YouTube) — https://www.youtube.com/watch?v=BIiGKk7OV9U

 

04 — Ready to migrate? Resources & feature parity

When you are ready to move, the good news is that getting started is simpler than you might expect. CWM and Agile 2.0 share the same story table, which means your existing stories and epics are already available in CWM with a simple setup. Teams can begin using CWM for sprint planning today using the Connected Work feature to surface their existing Agile 2.0 stories.

 

 

Migration Guide: Team-Level Agile from Agile Dev 2.0 to CWM — https://www.servicenow.com/community/cwm-articles/migration-guide-for-team-level-agile-from-agile-development-2-0/ta-p/3508312

 Detailed step-by-step guidance for migrating your team from Agile Development 2.0 to CWM, including feature parity mapping and known gaps