hi welcome to this video about digital product release today I'll be covering digital product releases adoption Journey this video will be most applicable to release admins release process owners and individuals interested in getting started with DPR I'll be highlighting service now's perspective on the maturity steps within dpr's adoption journey and the value you can expect to achieve at each stage those stages start with using DPR to manually track and validate release Readiness all the way through build custom release policies leveraging service now records and third party cicd tool data to automate release validation let's jump into it the graphic you see here is service announc perspective on the adoption Journey applicable for most customers aiming to implement DPR the x-axis denotes the relative maturity within DPR and the Y AIS denotes the relative realized value the first step in the adoption Journey focuses on defining a release process within DPR using release templates and leveraging tasks and approval tasks to manage release execution tasks are manual activities defined within DPR that are associated to relevant phases of a release and manual approval tasks or tasks that have approval tied to them at this level of maturity you're not yet integrating with third party tools or using automated datadriven policies for release validation at this stage the management of release execution requires the PM or release manager to manually check for completion of tasks within a release phase to certify that that phase is ready before before moving on to the next phase of a release despite the management of release Readiness being entirely manual at this stage you'll still get much of the key benefits of DPR you'll get visibility across product releases within DPR you'll have the ability to create changes with release traceability for auditability and perhaps most importantly you gain the ability to shift left validation activities things like Upstream reviews and approvals validation of test results and SEC security scans uh away from change which has historically served as the final gate before before production and instead you can have those checks happen earlier in the relevant uh release phase that they occur in in this uh DPR short video series that we're producing on community we also have videos showing users how to define approval definitions for approval tasks and also how to create a release template that leverages tasks and approval tasks for validation of phase Readiness and a release so please check those out the second stage of this adoption journey is where customers integrate with their release planning tools for example SPM or jira to enable the automatic import of release features and epics and other work items to simplify the release planning within DPR and provide visibility into what is being addressed in a particular release in the first maturity step customers would most likely be performing release planning entirely outside of DPR by leveraging this outof the boox integration top level features epics and work items can be brought into DPR and be planned into applicable release release versions for traceability into what's being built and modified within a release at this stage release execution continues to be mostly manual via task and approval tasks but there is an opportunity to use some of our outof the-box policies in the DPR video series we also have a video walking through how to connect to a planning tool and another video showing the Light release planning that occurs within DPR uh leveraging imported work items from those planning tools the third stage of this adoption Journey expands upon the cicd tool Integrations with DPR and leans into automating aspects of release validation with the out-of-the-box policies we ship with the DPR policy content pack by integrating with orchestration testing security tools and more relevant data is ingested by our devops data model that can then be used for automated data driven validation of things like existence of critical vulnerabilities code coverage or Test passing percentage note that this is the same devops data model and Integrations used in our devops change velocity product so if you're a devops change customer you might already have a lot of the work completed to be at this maturity step for DPR it's also worth noting though that uh you do not need to have adopted devops change to leverage the devops data model for DPR additionally with this devops data tied to each discrete release that data will also be Associated to change requests that are tied to a release and thus enable better RCA if an issue does occur helping reduce mttr in the DPR short video series on community we have a video walking through how to activate out of the boox policies and configure them to fit your needs the final stage of the DPR adoption Journey looks at expanding the policies leveraged by defining custom policies that fit your organizational needs additionally at this stage customers would look to use DPR in conjunction with complimentary products like devop change velocity to automate change creation from pipeline executions or irm to drive more integrated risk management and compliance building and using custom policies will allow customers to automate in a data driven way even more of their release validation I'll also note here that creating custom policies will require service now development expertise to do and this is a stage where we could see working with a partner being beneficial for a customer one final comment on this adoption journey is that any step can be your entry point based on your maturity and goals with DPR so don't feel that you need to start at stage one if you feel ready for stages Two Three or even four as a recap getting the first value a DPR isn't all that difficult or complex it can start simply with just moving your release processes to DPR and using manual activities and tasks that you can Define as you see fit to manage your releases also wherever you are in your maturity you can step into DPR at the stage that suits your needs and finally expect that you can grow your maturity with DPR over time we'll be continuing to invest in improving dpr's capabilities as well if You' like to refer to to any additional resources please navigate to the digital product release community site where we have other helpful videos and blogs