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.
Table of Contents
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 and we are encouraging existing Agile 2.0 customers to migrate to CWM. 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.
- 2029+ (Exact Date TBD) — 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 accepted. 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. |
02 — What changes between Agile 2.0 and CWM
Agile Development 2.0 was purpose-built for scrum teams. CWM is the platform-native layer for all work — agile, hybrid, and project-based — with a richer UI, automation, and a shared data model with the rest of ServiceNow.
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.
Translating Capabilities from Agile 2.0 to CWM
| Capability | Agile 2.0 | CWM |
| Sprint board | Sprint planning board with native sprints | Board + Sprint Planning view |
| Backlog | Built-in backlog on sprint board | Backlog section in Sprint Planning view |
| Work items | Stories and scrum tasks | Stories, scrum tasks + Connected Work for incidents, problems, project tasks, or any task-based table |
| Bringing in other work | Unified Backlog | Connected Work |
| Kanban / tracking | Sprint tracking board | Kanban view in CWM |
| Sprint history | rm_sprint table | New CWM sprint table - sn_cwm_sprint |
| Release Management | Field on the Story form | Same field; add to the CWM view to surface it |
| Epic backlog | Built-in epic backlog | Via EAP integration (native Epic backlog on the 2026 CWM roadmap) |
| Sprint history does not migrate. Agile 2.0 and CWM use different sprint tables. Begin CWM sprint planning from a clean sprint boundary — don’t attempt to import historical sprint data. |
03 — What stays the same
Your core agile work items — Stories and Scrum Tasks — sit on the same tables in Agile 2.0, CWM, and EAP. You are not recreating data. You are giving it a new interface.
| Work item | Table | Status |
| Story | rm_story | Shared — no migration needed |
| Scrum Task | rm_scrum_task | Shared — no migration needed |
| Defect | rm_defect | Shared; native UI in CWM on the roadmap. Today, bring in via Connected Work. |
| EAP Epic | sn_align_core_scrum_epic | Shared between EAP and CWM |
| EAP Feature | sn_align_core_feature | Managed in EAP |
| Connected Work task | task (platform) | Available in CWM |
04 — The artifact journey
Some artifacts used in Agile 2.0 don't map to CWM. Walk through each artifact below before deciding on a path.
Enhancements
Over time, Enhancements became a flexible — sometimes informal — container for work that did not fit neatly into other item types. Below common patterns that drove Enhancement adoption, each of which now has a more purpose-built solution.
Work smaller than a project, not necessarily agile
Enhancements offered a lightweight way to track and complete work that did not warrant a full project but still needed visibility and accountability. In CWM, a CWM task is the natural replacement for teams managing non-agile, task-based work.
Way to assign work to an agile
For teams that do follow agile practices, an Epic or a Story depending on the size of works, provides the same structured container without requiring a full project setup. Epics can be created in CWM, with the option to view/manage them in CWM is planned for H2 2026.
Operational improvements and internal product requests
Many teams used Enhancements to capture ongoing improvement ideas, product feedback, and internal requests that do not drive net-new capability.
The recommended path for this use case is Product Feedback (Idea), which supports an Enhancement Request category out of the box. An Idea portal can be configured to capture submissions, route them to the appropriate product or team, and provide status visibility back to the original requestor — all without custom development.
Quick reference: choosing the right path
| Scenario | Recommended Approach |
| Non-agile operational or task-based work | CWM task |
| Agile planning | Epics or Stories (based on size of work) |
| Internal product requests with requestor visibility | Product Feedback — Idea portal |
Note: Organizations currently using Agile Development 2.0 may continue using Enhancements until the retirement milestone. However, if you are onboarding new teams or users, we recommend adopting the replacement paths outlined above now. This ensures a smoother migration and avoids building further dependency on a work item type that will no longer be supported going forward.
Themes
Product Themes (rm_theme) also belong to the Agile 2.0 data model. They will remain a valid grouping mechanism on the Story form.
Recommendation: Use Epic- Feature- Capability hierarchy between CWM and EAP to group your work. You can also create a custom column at a table level (rm.story) or CWM board level to group working using a column.
Or, if you choose to continue the old table:
- Creation Path: Still on rm_theme, referenced from the Theme field on rm_story.
- Visibility in CWM: The Theme field is hidden by default in the CWM view. Add it back via the rm_story list view → Edit views → CWM view → add the Theme column.
- Not supported: Creating new Themes from the CWM Add Item button
Features
There are three legacy feature tables. Pick the right one for your context. OOTB CWM does not support feature creation or execution.
Recommendation: If you are moving to scaled agile, manage Features on sn_align_core_feature in EAP. Reserve rm_feature for legacy Agile 2.0 visibility only. EAP does not support rm_feature.
| Table | Purpose | Where it’s managed |
| rm_feature | Agile 2.0 compatibility. Surface in CWM via Connected Work for visibility only. | Agile 2.0 |
| sn_align_core_feature | Scaled agile execution — features owned by an ART or program. | EAP planning board |
| sn_dpr_feature | Strategic product visibility tied to Digital Product Release. | DPR |
Releases
Release planning was handled through the Release field on the Story form in Agile 2.0. The field still exists on rm_story — it is simply hidden by default in the CWM view.
- Creation Path: Create a release on your existing release table.
- Visibility in CWM: Open the rm_story list view and form view, click Edit views, select the CWM view, and add the Release field. Once added, it appears as a column on every CWM board that uses this view and the rm_story form in CWM.
- Digital Product Release (DPR): Native DPR integration with CWM and EAP is on our roadmap but not yet out of the box. Until it ships, the Release field on the Story is the interim traceability mechanism.
Epics
Recommendation: Use sn_align_core_scrum_epic for all new epic-level work. It is the shared CWM + EAP epic table. Epics created here are visible to multiple teams and flow correctly through EAP planning.
| Table | Used by | Status |
| rm_epic | Agile 2.0 (legacy) | Available — the Epic field on a story still points here. Bring into CWM via Connected Work. |
| sn_align_core_scrum_epic | EAP and CWM (shared) | Available — use for all new epic-level work. The Parent Work Item on a story populates from this when a parent-child link exists in EAP. |
| sn_safe_epic | SAFe (legacy) | Deprecated — do not build new integrations on this table. |
Today, EAP epics cannot be opened directly on a CWM board, but the Parent Work Item field on a Story will populate when a parent-child relationship is established in EAP. Native epic visibility on the CWM board is on the 2026 roadmap.
Defects
Defects are not available OOTB in CWM today but is the on product roadmap. Use Connected Work to bring them on to a board.
- Creation Path: Native defect creation from the CWM Add Item button is not yet supported. Create new defects from the Agile Development module or the rm_defect form, then connect them to the board.
- Visibility in CWM: Open Connected Work on your board, add rm_defect as a source table, and filter by Assignment Group or Product.
- Story linkage: Use CWM task dependencies and relationships to link defects to their parent stories for traceability or continue to use the platform defect- story related list view outside of CWM.
05 — Find your path
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.
Path A — 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 and 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
- Now Assist task generation
Learn more: Team-level agile planning in CWM
Path B — 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: CWM & EAP: Agile Planning and Execution at All Levels
Demo video: Unified Agile: CWM + EAP (YouTube)
| EAP requires SPM Pro/SPM Prime. CWM is included in all SPM SKUs. If your team currently uses Scrum Programs or scaled agile features in Agile 2.0, you will need EAP on SPM Pro or SPM Prime. |
06 — Table map by path
Each path inherits the shared Story and Scrum Task tables. The differences are everything around them — sprint, backlog, board, epic, and reporting. Use the maps below to plan your cutover.
Path A — Tables for CWM Only
| Agile 2.0 concept | Agile 2.0 table | CWM equivalent |
| Story | rm_story | rm_story — same table, shared |
| Scrum Task | rm_scrum_task | rm_scrum_task — same table, shared |
| Sprint | rm_sprint | New CWM Sprint table — start fresh; no history migration |
| Sprint Planning Board | Sprint board | CWM Board + Sprint Planning view |
| Sprint Tracking Board | Tracking board | Kanban view in CWM |
| Unified Backlog | Unified Backlog | Connected Work on the CWM Board |
| Story-to-story dependency | rm_dependency | Cross-type dependencies in CWM (broader scope) |
| Theme | rm_theme | Use custom field on table or CWM board |
| Release | Release field on Story | Same field; add to the CWM view |
| Enhancement | rm_enhancement | Connected Work only — cannot create from CWM Add Item |
| Defect | rm_defect | Connected Work — native UI on roadmap |
Path B — Additional tables for CWM + EAP
| Agile 2.0 concept | Agile 2.0 table | EAP equivalent |
| Scrum Program / ART | (requires SPM Pro/Prime) | EAP Agile Release Train |
| Epic (scaled) | rm_epic | sn_align_core_scrum_epic |
| Feature | rm_feature | sn_align_core_feature |
| Capability | — | sn_align_core_capability |
| PI Planning | — | sn_apw_adv_iteration (Planning Interval) |
07 — Migration steps
A proven sequence for a clean cutover. Follow these in order — the full step-by-step guide is linked here.
Step 1 — Confirm licenses and roles
Ensure your team members have CWM access. Agile leaders who need access to EAP (ART RTEs, Program Managers, Product Managers) require SPM Pro/Prime.
Step 2 — Create your CWM Space and Board
Each agile team gets one Space. Inside the Space, create a Board. Share the Space with your team’s user group.
Step 3 — Connect your Stories via Connected Work
Use the Connected Work feature on your Board to pull in active rm_story records assigned to your teams. Scrum Tasks come along automatically as children of their parent stories. Filter by Active = true to avoid importing closed items. Note: the first-time import limit is 100 items per condition (adjustable via sys_properties_list.do).
Step 4 — Recreate custom fields and columns
Org-wide fields (Release, Product, Theme, custom attributes): add to the CWM view of rm_story. Board-specific columns: add via List view → Add column.Document your Agile 2.0 custom fields as a checklist before starting.
Step 5 — Start your first CWM sprint
Switch to Sprint Planning view. Create a new sprint from a clean cutover date. Drag stories from the Backlog into the sprint. Hit Start. Do not attempt to import Agile 2.0 sprint history.
Step 6 — Run standups on the Kanban view
Use the Kanban tab for daily execution. Team members update cards live during standup. Use the gear icon to configure swimlanes. Filter to the current sprint to keep the board focused.
08 — Feature gaps
Reporting and analytics
| Gap | Current state | Recommended path |
| Sprint velocity, burndown, and burnup charts | CWM + EAP — EAP has native team-level sprint reporting today. CWM alone: build with Platform Analytics | Team level analytics will be supported in CWM starting Q3 2026. |
Work item creation and management
| Gap | Current state | Recommended path |
| Native Epic creation visible on the CWM board | The Create Epic button writes to sn_align_core_scrum_epic but the epic does not appear on the board today. Native visibility is on the 2026 roadmap. |
CWM today- For legacy rm_epic, use Connected Work for visibility only. CWM + EAP — manage epics in EAP; the Story’s Parent Work Item field populates when a parent-child link exists. |
| Native Defect creation from CWM board | rm_defect can be surfaced via Connected Work but cannot be created from Add Item button on CWM board. | CWM today — create defects from the rm_defect form or Agile Development module, then surface via Connected Work. |
| Native Enhancement creation from CWM Add Item | rm_enhancement can be surfaced via Connected Work but cannot be created from Add Item. Creation still happens from a Demand. | CWM today — Use CWM task type to create new enhancements. |
| Sprint Goals | Not available out of the box in CWM. | Use a custom field on CWM sprint table |
| Theme as a native board grouping | Theme field exists on rm_story, but CWM does not group stories by Theme on the board like Agile 2.0 did. | CWM today – Use Epics or custom column at board or table level. |
Integration with other modules
| Gap | Current state | Recommended path |
| Digital Product Release (DPR) ↔ CWM integration | Native DPR integration with CWM/EAP is on the roadmap but not yet OOTB. | Workaround — add the Release field on rm_story to the CWM view for story-level traceability. |
| CWM ↔ Project Workspace bidirectional sync | No native bidirectional sync today; on the roadmap. | Workaround — bring pm_project_task and demand tasks into CWM via Connected Work; use SPW Portfolio to surface project + CWM progress in one place. |
| Direct board-to-Demand or board-to-Project link | Boards contain work items, not container records. No direct link out of the box. | Workaround — model traceability through Demand → Epic (sn_align_core_scrum_epic) → Story; use Connected Work for project tasks. |
Migration
| Gap | Current state | Recommended path |
| Migrating historical sprint data from Agile 2.0 | rm_sprint and the new CWM sprint table are structurally incompatible. | start each team from a clean CWM sprint at cutover; keep Agile 2.0 read-only for history. |
|
Have a gap that isn’t listed here? The CWM team is actively gathering migration feedback. Raise it on the ServiceNow Community CWM forum or reach out through your account team — the 2026 roadmap is still being shaped. |
09 — Helpful links
- Full migration guide (Community): https://www.servicenow.com/community/cwm-articles/migration-guide-for-team-level-agile-from-agile-de...
- Team-level agile planning in CWM: https://www.servicenow.com/community/cwm-articles/team-level-agile-planning-in-cwm/ta-p/3486281
- CWM & EAP overview: https://www.servicenow.com/community/cwm-articles/cwm-amp-eap-agile-planning-and-execution-at-all-le...
- Unified Agile demo (YouTube): https://www.youtube.com/watch?v=BIiGKk7OV9U
- Configuring CWM (Product Docs): https://www.servicenow.com/docs/r/it-business-management/collaborative-work-management/configuring-c...
- Connected Work FAQ: https://www.servicenow.com/community/cwm-articles/cwm-connected-work-faqs/ta-p/3337946
- CWM Overview Video (YouTube) — https://www.youtube.com/watch?v=g--00jLY_M8
- Quick Guide to CWM Implementation — https://www.servicenow.com/community/cwm-articles/quick-guide-to-cwm-implementation/ta-p/2914658
