Blog : Collaborative Work Management (CWM) in ServiceNow - An Experience-Based View

[Hima V Dev]

Collaborative Work Management (CWM) in ServiceNow is often misunderstood as just another planning tool. In practice, it works best when it is not treated like a traditional project or agile framework.

CWM is centered around Spaces, which act as collaborative hubs rather than rigid project containers. This makes it especially effective for cross-functional initiatives, business-driven execution, and work that evolves over time. Teams can focus on outcomes and alignment instead of task-heavy governance.

From hands-on implementation experience, one important technical insight is that CWM work items are logical constructs, not records stored in a single dedicated table. They are surfaced through the UI and backed by underlying platform or SPM-related records, with visibility and access resolved dynamically based on Space configuration and membership.

This abstraction offers flexibility, but it also requires thoughtful design for reporting and traceability. When implemented with the right expectations, CWM becomes a powerful execution layer that connects strategy and delivery.

If you’d like to learn more about CWM implementation or discuss real-world use cases, feel free to reach out to me.

[Lillian]

Hi,

After deprecation, customers may continue using Agile 2.0 and its child applications as unsupported customizations (no technical support). However, ongoing investment and new AI-native capabilities are focused on CWM and EAP, so we encourage customers to evaluate migration when appropriate.

For additional guidance on migration, future roadmap capabilities, and EAP and CWM, please refer to the following resources:

Agile 2.0 to CWM Migration

Team-level agile guidance Community post and FAQs

Unified Agile Guidance community post

Unified Agile demo video

[Chris Doernbra1]

We released this application to help teams pull work in across various applications (INC,RITM, etc) as well as to create their own tasks. One day into this trial we came across what I think is a huge miss and will probably render this unusable for us. 

We had a team create filters to pull in work across RITM, INC and SCTASKS using very a simple filter: Assignment Group is XXXXXX and Assigned To is empty and Active is True. As expected the board gets populated with the resulting records. Some of these records were re-assigned to different teams after triage and what we found was that the records remain on the board even if you refresh. This leads to a lot of confusion and a board with records this team does not care about. 

I reached out to support thinking that perhaps there was a bug. This was the response:

This is expected behaviour by design. Consider connect work as import of work items from other tables into CWM board.
Hence, once records are imported with given conditions, they always persist.
We need to manually delete the records once created.

Currently, Connected Work pulls in work items matching connect work condition every time the board refreshes. However, the board doesn't automatically remove items that stop matching the condition. This isn't on our roadmap as of now. This is intentional: if you bring in all "Draft" incidents and start working on them, moving their state to "In Progress" would cause those items to disappear from your board. This would disrupt your workflow and create confusion as work items vanish mid-process.

NEXT STEP:
We suggest you to submit an enhancement request to raise this idea and add your business case to be reviewed as new functionality for the future release.

At this point I don't see the value in this application given the amount of manual work its going to take with clean up and the fact that I can't quickly link records or handle any of the agile functionality other than create stories.