---
sourceType: article
title: "Application Portfolio and Services Portfolio are Sibling Portfolios"
authors:
  - Bodman, Mark
  - Thigpen, David
url: https://www.servicenow.com/community/itsm-blog/application-portfolio-and-services-portfolio-are-quot-sibling/ba-p/2268961
license: third-party
abstract: |
  ServiceNow community blog. Mark + David Thigpen explain why Application
  Portfolio Management (APM, Dev side) and Services Portfolio Management
  (SPM, Ops side) belong in one platform on a shared data model rather than
  in separate tools glued together. Foundational to the four-year Digital
  Portfolio Management arc that merged the two. Third-party publication;
  abstract + locator per RAW-SOURCES-LICENSE.md.
---

## Why it's cited

Backs the position that **portfolios are siblings; they live in one house** — an operational corollary of the EA-consolidation stance.

## Key claims (verified verbatim against source)

- The article's title is the position itself: *"Application Portfolio and Services Portfolio are 'Sibling' Portfolios That Should Live in the Same House."*
- Bodman + Thigpen on the platform argument: *"It didn't take much for me to see the benefits of managing both portfolios on a single platform."*
- The structural argument is framed via a shared CMDB, not via a single management product: *"Having the portfolios within a single source CMDB adds dimensions that cross the planning domain, architecture domain, service domain, and operational domain."*
- Why integration alone doesn't fix it: *"When managing them in silos, you sometimes need to use the scream test… Being part of a shared CMDB provides that high fidelity 'map' of dependencies — no need to try and marry these key portfolios from multiple systems."*

## Attribution caveats

- This article does **not** use the term &#34;Digital Portfolio Management&#34; or &#34;DPM.&#34; The DPM framing comes from a later 2022 LinkedIn post announcing the merged product. Don&#39;t cite this article as the source for &#34;DPM.&#34;
- The article does **not** include the &#34;DevOps work at an enterprise level&#34; quote that earlier drafts attributed to it. That phrasing is from the 2022 DPM overview LinkedIn post, not this community blog. Pages quoting it should cite the 2022 post instead.

## See also

- Stance: `[[stances/dont-integrate-ea-platform]]`
- Entity: `[[entities/portfolio]]`
- Entity: `[[entities/csdm]]`
