Digital Product Release: Application Models vs. Service Models

Joe Offenberg

If you've implemented Digital Product Release (DPR), you've likely encountered one of its earliest and most consequential decisions: should you use an Application Model or a Service Model? The choice might seem subtle at first, but it shapes how your teams organize ownership, track releases, and connect delivery work to the services and applications your business depends on. Understanding the difference — and knowing when to use each — is the foundation for getting real value out of DPR.

The choice depends on what you're releasing and how your organization structures ownership.

Application Models

Use when releasing a discrete software application with its own development lifecycle:

The release is tied to a specific app (e.g., a mobile app, internal tool, microservice)
Teams are organized around application ownership (e.g., an app team owns all releases for that app)
You want release templates scoped to a particular application's phases and tasks
Common in software/product engineering contexts
Release Scope is tied to planning work item like stories and epics in SPM, ADO, or Jira
You need to track versions at the application level using semantic version numbers e.g. 12.2.5, 12.3.0

Service Models

Use when releasing changes to an IT service or a capability consumed by the business:

Aligns with the traditional ITSM/ITIL Service Transition Model
The release affects a service (e.g., HR Service Delivery, Customer Portal, ERP)
Multiple applications or components contribute to a single service release
Teams are organized around service ownership (e.g., a service owner coordinates releases across systems)
Common in enterprise IT or shared services contexts
Versioned by release date, month, quarter, e.g. MAY26, JUNE26, Q324
Release Scope would include resolving ITSM tasks such as Problems, Catalog Requests, Demands, Incidents, etc...

Example Scenarios

Scenario	Use
"We're releasing v2.3 of our Payments App"	Application Model
"We're releasing our Q2 HR Portal update"	Service Model
Dev team owns the release end-to-end	Application Model
IT/ops team coordinates across multiple apps	Service Model
Tied to a CI in the CMDB as an application	Application Model
Tied to a CI in the CMDB as a business service	Service Model

Both model types use the same underlying schema to define the release process. (sn_dpr_model_release_template) — the distinction is really about what CI type anchors the release and how your org maps ownership. In practice, many enterprises use service models for IT-managed releases and application models for product/dev-led releases.