Agile/DPR Products for ServiceNow Applications

[Community Alums]

Hi All.

I'm looking for some feedback on how to leverage Digital Product Release for ServiceNow development teams. Specifically, I'm looking for feedback on what Products anyone else has created for use with Stories and Release. I've seen examples that recommend two paths:

1. create products that align with platform areas (ITSM, CSM, ITOM, etc).
2. create products that align with with applications (Incident Management, Problem Management, Change Management, Advanced Work Assignment, Agent Client Collector for Visibility, etc)
   1. This option seems to align with the Starter Stories that ServiceNow has posted on Now Create.

[Dr Atul G- LNG]

Hi @Community Alums 

I will vote for 2nd option, as if you go like product ITSM / ITOM , it is very wide in nature and then it is tough for you to track the same as well, and module level like incident / change etc. which is used and known by every one and this way easy to track as well and 2ndly, it is as per starter stories. 

[Colin OBrien]

Hi @Community Alums,

The rule of thumb that I use is to track whichever level that you need to track the Release at. If you don't need to track releases (including the enhancements/epics/stories) at the level of Incident, Change, Digital Product Release, then you can just make an ITSM product instead of the child products. Usually, customers create products represented with your second option, just like @Dr Atul G- LNG said.

The reason that I came back to this post is that starting with the August release (DPR v1.2), you can model a hierarchy of products if that is valuable for your organization. You can create an ITSM product, navigate to the Included Products tab within the product and add Incident, Problem, Change, DPR, etc. as child products.

Planned for DPR 2.0 in February 2025 (disclaimer about futures are subject to change), you will be able to create a multi-product release where you can create a release for ITSM and we will pull in the included products to create one consolidated release. You can plan and validate each of the included products while having one release record to manage the process.

Cheers,

Colin

[Community Alums]

Hey @Colin OBrien,

Thank you for your feedback. A multi-product release is exactly what I've been looking for. My team and I have been evaluating DPR for implementation, but it didn't align with our organizational structure without the multi-product release feature. I know we're a few weeks before February, but could you please provide any documentation or videos that showcase the features of DPR 2.0?