Release Management - Use case

[Tommaso2]

Hi all,

Can you please provide one or more easy use cases for Release Management?

For example: which are the steps to release a project or an incident?

As far as I understood it is possible to associate projects, incidents, problems and so on with a release and then the implementation is done always with a change request.

To better organize the release it is possible to create phases, assign task manually in each phase, schedule the release. This is just theory, one or more end-to-end easy use cases would be very helpful.

Many thanks,

Tommaso

[Dr Atul G- LNG · Accepted solution]

Hi @Tommaso2 

If you're speaking from the ServiceNow perspective, the plugin previously called Release Management no longer exists. It has been replaced and enhanced by a new product called DPR – Digital Product Release.

DPR is more powerful and serves as a single-stop solution to manage your product journey—from Idea to MVP/Go-Live. You can also link or integrate DPR with SPM and Agile, and it includes DevOps integration as well. 🚀

Here’s a video I created based on the older version, and I’m also sharing another link that highlights the latest features of DPR:

https://youtu.be/OjLdfawvBZI

https://www.servicenow.com/community/digital-product-release-blogs/what-s-new-in-digital-product-rel...

[Dr Atul G- LNG · Accepted solution]

Hi @Tommaso2 

If you're speaking from the ServiceNow perspective, the plugin previously called Release Management no longer exists. It has been replaced and enhanced by a new product called DPR – Digital Product Release.

DPR is more powerful and serves as a single-stop solution to manage your product journey—from Idea to MVP/Go-Live. You can also link or integrate DPR with SPM and Agile, and it includes DevOps integration as well. 🚀

Here’s a video I created based on the older version, and I’m also sharing another link that highlights the latest features of DPR:

https://youtu.be/OjLdfawvBZI

https://www.servicenow.com/community/digital-product-release-blogs/what-s-new-in-digital-product-rel...

[Tommaso2]

Hi, thank you for your support!

We are pushing our client to use DPR rather than Release Management, but tomorrow we have a scheduled call to show ootb functionalities of Release Management and I have doubts about a standard use case that can be presented:

- There is the "Phase" field with ootb values (such as "Requirement gathering" and so on) and also there is the related list where new phases can be created from scratch: which is the relationship between that field and the related list?

- Tasks have to be created against the "Phase" field or the phases in the related list?

- In a release it is possible to associate projects, incidents and so on from the related lists, it is just for tracking purpose right? Can you please provide a real case scenario?

Can you please provide an easy end-to-end use case that includes phases with tasks and project/incident and so on association?

Many thanks,

Tommaso

[Dr Atul G- LNG · Accepted solution]

Hi @Tommaso2 

 There is the "Phase" field with ootb values (such as "Requirement gathering" and so on) and also there is the related list where new phases can be created from scratch: which is the relationship between that field and the related list?

Atul: Yes, the OOTB Phase attribute is available. If you want, you can create your own custom phase as well. For demos, I usually prefer to use the demo data and explain that we can create new phases when required.

- Tasks have to be created against the "Phase" field or the phases in the related list?

Atul:

Yes, each phase has tasks associated with it. For example, in the Requirement Gathering phase, tasks can include:

• Stakeholder meeting

• Agenda sign-off

All tasks should be linked to at most one phase of the release.

- In a release it is possible to associate projects, incidents and so on from the related lists, it is just for tracking purpose right? Can you please provide a real case scenario?

Atul:

Yes, to link the projects, you need to install the SPM (Strategic Portfolio Management) plugin. Once installed, the SPM component will be available for use in Release.

As I mentioned, the DPR process goes from Idea to Go Live.

Real case 

You’re done with Release 1 (R1) and now preparing for Release 2 (R2). Due to BAU activities, any incident that requires L3 support should be linked only with R2.

Ideally, you would create a change request and link the incident to the change. Alternatively, if you prefer, you can link the incident directly to the release or known errors as well.

https://www.servicenow.com/community/digital-product-release-forum/digital-product-release-using-ser...

[Tommaso2]

Hi,

Another point that is quite confusing to me is: if we want to release a project, the developments are already managed with project tasks, right?

Why in the release we also have WIP state that means that developments are ongoing?

It means that if project is in the execution/delivery phase then the release manager has to manually set the release record on "WIP"?

This is not clear to me when the release process starts, real use cases would be useful as usual.

Many thanks,

Tommaso