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.
