Collaborative Work Management - Concerns About Functionality

[Joanna Węgrzyn]

Dear ServiceNow Community,

As we are preparing to transition from Agile Development 2.0 to Collaborative Work Management (CWM), I am currently working to better understand the new functionality in order to be well prepared for the upcoming change.

I reviewed and examined all available documentation and instructional videos.

I have been exploring CWM in my PDI (Zurich) and have installed it several times for testing purposes. My initial plan is to deploy CWM on a clean instance where Agile Development 2.0 has not been used previously.

Based on my observations, CWM appears to still be under active development, as its behavior and feature set seem to evolve over time. For example, a few weeks ago when I installed CWM, Agile Development 2.0 was installed alongside it. However, when I installed CWM again this week, Agile Development 2.0 was no longer installed, and I noticed that several functionalities were missing. For this reason, I would appreciate your guidance in order to properly plan the implementation.

1) I have reviewed some available timelines, but I would like to understand whether organizations that plan to implement CWM from scratch, without having previously used Agile Development 2.0 - are included in these timelines. What guidance exists for organizations planning to implement CWM between Q1 and Q3 of 2026?

2) I have also observed that CWM stories currently lack several important relationships, such as dependent stories, prerequisite stories, and relationships to related records (for example change requests). Is there a roadmap to introduce these capabilities? Furthermore, is there a planned or supported way to create a story directly from an RITM when implementing a requested feature?

3) I also note that there is currently no application menu for agile-related functionality. Is there a plan to introduce this in the future, including the possibility to open views such as a table of stories, similar to what was available in Agile Development 2.0?

4) When opening the "rm_story" table, I do not see a "New" option to manually create a story. Does this mean that story creation will only be possible through CWM going forward? If so, is this an intentional design decision?

5) During story creation in CWM, I noticed that it is possible to set random ID for story.

At the same time, I am unable to configure the story number field as read-only via form design.

Is it possible to customize the story form to meet company-specific requirements? I attempted to edit the story form using the CWM view, but the changes are not reflected in the CWM Workspace.

6) Additionally, I noticed that fields such as Product, Theme and Release, are not available. Is there a plan to introduce these elements? More generally, what will be the future structure for agile-related data and processes in ServiceNow?

7) I have an additional question: CWM - Why is the “Assigned to” filter unavailable in the Kanban view, unlike in VTB? (I am unable to respond to my own posts in the Community , therefore, I will repeat it here; The question may not be "why it is not there", but rather "whether it will be there").

I understand that VTB and CWM are different products, however, since CWM is intended to be the recommended tool for Agile in ServiceNow, I would like to clarify its capabilities.

I would like clarification on whether it will be possible to filter stories by "Assigned to" during stand up meetings. My original question aimed to confirm whether such functionality exists, whether I may have overlooked a configuration option, or whether there is an alternative approach.
This capability is a critical core feature, as it significantly improves the efficiency of collecting status updates during daily stand up meetings. While I am aware that stories can be sorted by specific columns or grouped using horizontal lanes, this approach does not provide an optimal user experience for stand up meetings.

Thank you very much for your time, review, and any guidance you can provide.

[Peter Spuijman]

Hi Joanna,

We're using both Agile V2 & CWM within our company.

CWM looks promising and capable of surpassing Jira in terms of userfriendliness & flexibility.

At this moment, I do not consider it a sufficiently mature product (confirmed by most of our development squads)

- migrating from Agile V2 to CWM is difficult if you want to conserve history

- it can retrieve tasks, but it's lacking in functionality vs. a triage board

- it remains unclear on how it will integrate with Enterprise Agile Planning

Hence at this moment, CWM is deployed but rather to replace smaller Jira teams and Microsoft planner functionality as it has the advantage of being connected to the whole platform.

Burnup/Burndown charts OOB are apparently not foreseen before Q4 2026, so at this moment we are sticking to Agile V2 which still has the edge.

Hope this helps

Warm regards,

Peter

[Adam Geil]

We're in a similar position. CWM seems very promising, but the product isn't fully mature yet. I'd recommend waiting until the Australia release in May and reviewing what features/fixes are released before switiching over.

[Sunil B N]

Hi Joanna,
Thanks for the detailed and analysis and questions. 
1. We will be publishing guidance about this soon. I will have it linked here once its available.

2. Dependencies are available as part of Q1 2026 (March release). CWM v9.x
3. We will definitely look into this. OOTB at the moment there is no menu as part of CWM.
4. There are technical things which connect story to a specific CWM Board. If you have agile 2.0 - it will continue to allow creation of Stories outside CWM.

5. We will look into this. Ideally should not be editable. Can you try as non-admin?
If issue persists for non-admin, as a workaround - A business rule would do the job.

6. We have plans to integrate with Digital product release (DPR) in our roadmap.

7. Its crucial to have filters in Kanban. With CWM v9.x (Q1 March 2026) release, you can filter using any fields in Kanban.

Thanks again for these insightful questions. Keep them coming.
Best Regards,
Sunil B N

[Joanna Węgrzyn]

Hi @Sunil B N,

Thank you for your investigation and for the response provided.
I would appreciate it if you could share your guidance directly here.

With regard to point 4, the main issue is that we are starting with a clean instance that does not include Agile Development 2.0. As a result, there is no data available to transfer. It appears that this scenario was not taken into consideration, and we are therefore required to track our project in JIRA, as it seems that for a clean instance without Agile Development, this functionality will not be available to us.

Following your guidance, I retested point 5 by impersonating a user with only the “sn_cwm.cwm_user” role. In this case, the story ID is displayed in read only. However, we still face a limitation, as it is not possible to create a custom design of the story form that would be reflected in CWM.

Could you please advise when the integration with the Digital Product Release (DPR) is planned on your roadmap?

Additionally, will the filters in Kanban be similar to those previously available in VTBs, allowing us to quickly select names and view stories assigned to a specific person?

Thank you for your continued support.

Kind regards,
Joanna