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.

[Hima V Dev]

That’s a fair point, and I agree this is how many teams are currently approaching CWM, primarily as a successor to Agile 2.0. In fact, most implementations I’ve seen start exactly there, focusing on sprint execution and team-level delivery.

However, from implementation experience, CWM’s real strength starts to show beyond pure Agile use cases. The Space-based model works well not only for Agile teams, but also for cross-functional initiatives, business-led execution, and work that doesn’t fit cleanly into a traditional Agile or project structure.

I like your suggestion about a migration-focused blog.  “Agile 2.0 → CWM” perspective would be a practical way to highlight both the functional mapping and the additional capabilities CWM brings, especially around collaboration and outcome-driven planning. I’ll definitely consider writing a follow-up post on that.

Thanks for sharing your thoughts..

[Chris Doernbra1]

I have started to look into CWM and how to migrate to it from Agile and I am finding that it's not so simple. Yes you can create a board and pull in all your teams work but there are many limitations. We use Demand and from there you can create defects and enhancements. From those records you can create stories. From my understanding Demand doesn't go away and perhaps the agile tables don't either but in CWM I don't see the ability to open a demand and create these next step records. I don't see an option to even create the CWM tasks and tie them to the demand. If you create a story you can then open that story and tie it back to the demand/enh/defect but that is so much more work than the current method. Maybe this isn't how it's envisioned to be used?

[phil_bool_unifi]

As a partner, I work with a lot of customers who are using Agile Dev 2.0 with integrations to ADO or JIRA to handle the agile fulfilment steps of their SPM journey, integrating the results seamlessly back to the Demands and Planning Items, so their percentage complete, dependencies and targets can be kept up-to-date easily.  

The role of CWM as a powerful and versatile fulfilment tool that gives PM's the ability to create the right work structure and manage tasks in an environment with fewer restrictions seems powerful but not aligned to their needs, and I'm struggling to convince them this is really ready for that purpose.  Even my best demos do not seem to hit the mark.

This on top of the fact that customers with the historic Scrum Team SKU would now have to pay additional licensing to access CWM is making this a tough journey to manage, and even some of my longest-standing customers are concerned about this.  Some are even looking at other tools, or talking about shifting some key SPM reporting out of SN to their (previously integrated) Agile Tools.

I'd love to join a blog, or dedicated thread where we can keep exploring this.

[Chris Doernbra1]

I agree, I am really struggling with the fact that the suggestion is to transition to CWM or EAP. EAP really only works if your organization is hard core agile. It's entirely too deep for organizations using minimal agile 2.0 functionality. CWM on the other hand has a lot of usual features but it is extremely limited for those of us that will need to transition from 2.0. 

The more I read it seems like though agile 2.0 will go away, it looks like the underlying tables will remain because some of them will be used with CWM. If this is the case can we not just continue using the Agile 2.0 tables? I would have to assume the underlying tables and functionality will not go away, they just won't support/upgrade it. As an existing user this might be the better approach until CWM is further developed.

[Peter Spuijman]

Agree with you Chris, at this moment CWM is quite enticing but it does not have the maturity of Agile V.2 yet .  Our smaller teams however find the 'unified backlog' very handy, but it doesn't cut it yet for squads handling large backlogs - they prefer the triage boards.  And even with legacy Agile V.2 you can go quite far, even if the look & feel aren't as modern.