Challenges fitting CWM, SPW, and EAP together after Agile 2.0 deprecation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2026 11:49 AM
Hi Vera,
Would you like to get together to discuss as there is some overlap in the options. If so, just send a quick email to me to coordinate (william.townsend@servicenow.com)? I may also pull in a colleague from the DPR side.
In terms of DPR materials, here are a couple of resources:
https://www.youtube.com/watch?v=WF4SEqLWEIM
Thanks,
Scott
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2026 12:44 AM
Given all of the above, we are questioning whether the Digital Product lens is actually the right fit for our context.
Would you recommend using the Digital Product lens, or would it be more appropriate for us to define a custom lens aligned with our operating model? For example:
- Product → Themes → Epics, or
- Product → Features → Capabilities → Epics
From your experience:
- When is the Digital Product lens the recommended approach?
- When does it make more sense to create a custom lens?
- What criteria should be used to decide the right hierarchy when evolving from Agile 2.0 towards SPM Pro and SAFe?
Any guidance or best practices on how to position these constructs would be greatly appreciated.
