Release Mgmt & Digital Portfolio Mgmt
About 1% of the CIS-SPM exam — see all 10 domains.
Release Management (RM v2, documented in the IT Service Management book) coordinates releases whose scope can include projects, epics, stories, and problems; Agile Development adds release dashboards and the scrum program planning board for planning across teams. Digital Portfolio Management (DPM Workspace) manages solutions (services, service offerings, business applications, and service instances) across plan, build, and run, with KPI groups and data pulled from related applications such as Enterprise Architecture (formerly Application Portfolio Management). 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 Agile boards, sprint cadences, and team backlogs for the product teams that build and maintain each service
- B. Score and rank the incoming demands for each service on risk, value, and size using the Demand Workbench bubble chart
- C. Manage services, service offerings, business applications, and service instances across their plan, build, and run life cycle ✓
- D. Submit and approve weekly time cards for the support and enhancement work that service owners perform on business applications
Why: The DPM Workspace is a single place to manage solutions (services, service offerings, business applications, and service instances) through plan, build, and run, tracking them with KPI groups and data pulled from across the platform. Configuring Agile boards and sprints belongs to agile delivery tools, scoring demands on the bubble chart belongs to Demand Management, and submitting and approving time cards belongs to Time Card Management.
In Release Management, a release is best used to:
- A. Allocate individual resources from a resource group to the release tasks of each product for the current sprint
- B. Approve the funding of the projects, programs, and demands in a portfolio for the selected fiscal planning cycle
- C. Group and coordinate the delivery of features/work to be deployed together across one or more projects/products ✓
- D. Score and prioritize incoming demands for a product before they are converted into projects or enhancements
Why: A release bundles work (projects, epics, stories, enhancements, defects, problems, and so on) for products or services so it is built, tested, and deployed together, organized into release phases and release tasks. Allocating resources is done through Resource Management, approving portfolio funding is portfolio planning, and scoring demands is demand assessment.
A customer wants to coordinate a 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. Release Management and DPM are the same capability presented under two names, so either one can plan the multi-project release, its go-live, and its rollback
- B. DPM schedules the release phases and tasks, while Release Management retires the business applications that the release replaces
- C. Release Management coordinates releases within one project at a time, so DPM is used to combine the three projects into one go-live
- 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 (its phases, tasks, and deployment), and DPM governs the broader solution and application portfolio life cycle that the release touches. They are distinct capabilities, not one feature under two names; DPM does not schedule release phases and tasks, and Release Management does not retire applications; and a release can bundle work from multiple projects, so DPM is not needed to combine them.