Agile Product alignment with CSDM

[Bradley Ross]

When using the Agile Development module, you create "products" which are stored in the software model table. What is the relationship envisioned in the CSDM for these "products"? Should they relate to Services? to Service Offerings? to Business Applications? Rather than linking to those other CI classes, should we instead be using them directly instead of using the model table?

[Melissa Barnes]

This topic hasn't been updated in a few years - any new guidance as CSDM v4 is out? I think it becomes even more complex as there is a transition to SAFe agile. Curious if any of the CSDM experts have input. 

[s4scott]

If anything, it is much more straightforward to track application portfolios with CSDM in light of SAFe 6.0. Products are tracked as Business Applications - This is the top level of the portfolio
Implementations of those products are tracked as Application Services. This is where the model version information for the product is surfaced. This is where product delivery is managed.
Component objects of the Application Service are tracked in the classes under the Application Server parent class. These are the CIs that teams would update with daily/weekly/monthly releases.

Tracking model version data in the Application Service and Application Server classes rolls up to the Business Application to show variation across implementations and highlight planning and lifecycle needs.