Release Mgmt & Digital Portfolio Mgmt
About 1% of the CIS-SPM exam — see all 10 domains.
Release Management (in the Agile/Project context) groups work into releases and supports release dashboards and the scrum program planning board to plan program increments across teams. Digital Portfolio Management tracks the lifecycle, health, and investment of applications/products (a business/technology portfolio of digital assets), linking products to the work and money behind them. Smallest domain — know the concepts, not deep config.
Sample questions from this domain
Three of the 3 in this domain, with the reasoning. The full set is in the question bank.
Digital Portfolio Management (DPM) primarily enables organizations to:
- A. Configure sprint boards
- B. Set functional currency only
- C. Manage business applications/products and align technology investments to business capabilities and value ✓
- D. Submit time cards
Why: DPM manages business applications/products and aligns technology investments with business capabilities/value. It is not time entry, sprint config, or currency-only.
In Release Management, a release is best used to:
- A. Allocate individual resources
- B. Define functional currency
- C. Group and coordinate the delivery of features/work to be deployed together across one or more projects/products ✓
- D. Score demands
Why: A release groups and coordinates work deployed together across projects/products. It does not allocate resources, score demands, or define currency.
A customer wants to coordinate a coordinated software release that bundles features from three projects with a planned go-live and rollback plan. Which SPM capability fits, and how does it relate to Digital Portfolio Management?
- A. They are the same feature with different names
- B. DPM schedules the release tasks while Release Management retires applications
- C. Neither supports multi-project releases
- D. Release Management coordinates the multi-project release delivery, while DPM governs the broader application portfolio lifecycle the release affects ✓
Why: Release Management coordinates the cross-project release, and DPM governs the broader application portfolio lifecycle that the release touches. They are distinct (not identical), DPM does not schedule release tasks, and both are relevant to multi-project releases.