Built something you're proud of? Tell the story. A quick G2 review of App Engine or Build Agent helps other developers see what's possible on ServiceNow. Share your experience.

Challenges fitting CWM, SPW, and EAP together after Agile 2.0 deprecation

Vero Moral
Tera Expert

‎03-30-2026 08:33 AM

In our organization we are currently using Agile Development 2.0. Given the deprecation notice, we are evaluating CWM, SPW, and EAP.

 

Our Agile 2.0 teams can be progressively migrated to CWM, while at the same time we implement SPW and adopt the Digital Product lens, using the following artifacts: Product, Product Feature, Product Enhancement, and Epics Planificable (sn_align_core_scrum_epic), synchronized with execution epics (rm_epics).

 

Some teams require the ability to work with Scaled Agile, which is why we are also considering EAP. The main challenges and questions we are facing are:

  • How can we import Agile 2.0 stories into EAP?
  • How are Product Features and Product Enhancements in SPW related to or synchronized with Capabilities and Features in EAP?
  • If a team works in EAP using Capabilities and Features, how can they perform digital product strategic planning using Product Features and Product Enhancements?

In short, we are struggling to understand how to properly fit CWM, SPW, and EAP together in a full configuration.

 

Thanks in advance

0 Helpfuls
  • 1,074 Views
6 REPLIES 6

Vero Moral
Tera Expert

‎03-30-2026 09:01 AM

VeroMoral_0-1774886294414.png

  1. Is this the correct relationship between the different objects?
  2. Is there any integration or linkage between Capabilities and Product Features?
  3. Is there an integration or relationship between Features and Product Enhancements?
  4. Which tables are used for each of these objects?
  5. Are these completely different objects, or do they share a common data model?
  6. How are these objects related to stories and epic?
0 Helpfuls

Anand__99
Kilo Sage
In response to Vero Moral

‎03-30-2026 10:34 AM

Hi @Vero Moral ,

 

Refer below document from ServiceNow related to SPM Architecture/Data Model.

Assets | Best Practices | ServiceNow

 

@Namita Mishra - Could you help?

 

Thanks

Anand

Scott Townsend1
ServiceNow Employee

‎03-30-2026 02:25 PM

Hi Vero,

 

We may want to have a meeting to discuss but let me add a few responses here to begin: 

  • How can we import Agile 2.0 stories into EAP?  EAP and Agile 2.0 both use the rm_story table.  The difference is that EAP uses the EAP Team (which has a 1:1 association with agile groups).  Once the story is assigned to the team, it will appear in EAP.  
  • How are Product Features and Product Enhancements in SPW related to or synchronized with Capabilities and Features in EAP?  Product Features and Product Enhancements (both used in DPR) are separate attributes from EAP Capabilities and EAP Features.  DPR's product features are long-living 'features' of a product while EAP features represent work to be done.  DPR's product enhancements are groupings of work to enhance a DPR feature (while an EAP capability which aligns with the SAFe methodology's capability - basically a feature done across 2 or more ARTs) .    
  • If a team works in EAP using Capabilities and Features, how can they perform digital product strategic planning using Product Features and Product Enhancements?  Before I go too far, are you using the DPR (digital product release) functionality?    

Thanks,

Scott (william.townsend@servicenow.com)

Vero Moral
Tera Expert

a month ago

Hi and thanks for your replies!

 

At the moment, we are using Agile Development 2.0 with Products (cmdb_application_product_model).
Related with these products, we define Themes, which we use as large functional blocks or major product capabilities.
Execution is then managed through Epics and Stories, and we reference with themes.

Recently, we upgraded from SPM Standard to SPM Pro, and we are now assessing the new capabilities and workspaces, especially if Agile 2.0 is planned to be deprecated.

 

While reviewing Strategic Planning Workspace (SPW), we noticed the Digital Product lens, which introduced us to Product Features and Product Enhancements.

Based on their description, we initially assumed that Product Features and Product Enhancements could replace our current Themes as higher‑level product constructs.

  • Is it correct to think of Product Features / Product Enhancements as a replacement for Themes, or is this a wrong assumption?
  • What is the intended role of these artifacts within the overall product and portfolio model?

 

In parallel, some of our teams are requesting SAFe capabilities, which led us to explore EAP Features and Capabilities.

This raised additional questions for us around positioning and governance:

  • How should EAP Features and Capabilities coexist with Product Features and Product Enhancements?
  • What is the recommended way to govern and use Product Enhancements, Product Features, Features, Capabilities, and Goals together?
  • Do any of these artifacts formally replace Themes, or should Themes be retired in a different way?

 

Finally, we would like to better understand DPR (Digital Product Release):

  • When and how should DPR be used?
  • In which scenarios does it add the most value?
  • Do you have any presentations, reference material, or workshops that explain DPR usage and best practices

 

Thanks!!!!

0 Helpfuls