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
2 hours ago
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
an hour ago
- Is this the correct relationship between the different objects?
- Is there any integration or linkage between Capabilities and Product Features?
- Is there an integration or relationship between Features and Product Enhancements?
- Which tables are used for each of these objects?
- Are these completely different objects, or do they share a common data model?
- How are these objects related to stories and epic?
