SPM Applications Overview
About 20% of the CIS-SPM exam — see all 10 domains.
A broad domain testing how the SPM suite fits together end to end and the role of each application.
The SPM value stream (strategy → execution): Strategic/Portfolio Planning → Idea → Demand → Project / Agile (Epic-Feature-Story) → Resource & Financial planning → Delivery → Benefits/PA reporting.
Core applications to know:
- Innovation Management: capture and evaluate ideas (Idea Portal, Idea modules).
- Demand Management: assess and prioritize proposed work (Next Experience for Demand Management; classic Demand Workbench).
- Project Portfolio Management (PPM) / Project Management: plan and deliver projects (Project Workspace; classic Planning Console).
- Resource Management: supply and demand of people; resource assignments in Resource Management Workspace (current) and resource plans (classic), capacity.
- Agile Development 2.0: scrum delivery on the Agile board (Backlog, Sprint Planning, Sprint Tracking with Story and Task boards). SAFe is delivered by separate Essential SAFe and Portfolio SAFe applications, and Enterprise Agile Planning (EAP), which includes a Kanban configuration, runs in the Strategic Planning Workspace (SPW).
- Test Management: test planning and execution tied to stories.
- SPM Financials: cost plans, benefit plans, budgets, and expense lines (actual costs) across demands, projects, and epics.
- Time Card Management: time capture against tasks, projects, and time card categories.
- Portfolio Planning Workspace / Strategic Planning Workspace: prioritize, roadmap, scenario-plan; goals/OKRs/targets.
- Digital Portfolio Management (documented in the IT Service Management book): manage solutions (services, service offerings, business applications, and service instances) across plan, build, and run. Application rationalization lives in Enterprise Architecture (formerly Application Portfolio Management), a separate application.
- Performance Analytics (PA), Reporting & Dashboards: KPIs and trends.
Plugins & store apps. SPM capabilities are delivered via plugins/store apps (e.g., Project Portfolio Suite with Financials, Demand Management, Resource Management, Agile Development 2.0, Portfolio Planning). Know that SPM Pro and licensing tiers gate certain workspaces. Many tables retain the legacy pm_, dmn_, resource_, time_card prefixes and "ITBM" wording.
Data model spine to memorize: Idea → Demand → Investment object; a Project/Demand/Epic is associated to an Investment that carries Cost Plans, Benefit Plans, and Budget. Portfolios are collections of related programs, projects, and demands; programs group related projects.
Sample questions from this domain
Three of the 60 in this domain, with the reasoning. The full set is in the question bank.
In ServiceNow SPM, which record type represents a high-level business need that has not yet been approved for funding or execution?
- A. Program
- B. Story
- C. Demand ✓
- D. Project
Why: A demand represents a proposed body of work or business need under evaluation before it becomes approved work. A project is approved, executing work, a program groups related projects and demands that are already being managed, and a story is an agile work item delivered by a team.
Which SPM application allows end users to submit innovation suggestions through a service portal for later evaluation?
- A. Innovation Management (Ideas) ✓
- B. Collaborative Work Management
- C. Enterprise Agile Planning
- D. Strategic Planning Workspace
Why: Innovation Management captures ideas, typically through the Idea Portal, for crowdsourcing and evaluation by idea managers. Collaborative Work Management organizes team work on boards and lists, Enterprise Agile Planning plans agile delivery across teams, and Strategic Planning Workspace is for portfolio planning, so none of them is the end-user portal for submitting innovation suggestions.
A demand that is approved can be converted into which of the following downstream records in SPM?
- A. A program, a portfolio, a goal, or an idea
- B. A release, a resource plan, an idea, or a goal
- C. A portfolio, an idea, a time card, or a rate card
- D. A project, an enhancement, a defect, or a change ✓
Why: Once approved, a demand is converted into an artifact that depends on its Category and Type, such as a project, an enhancement, a defect, or a change (with the right applications installed, also agile or EAP entities). It is not limited to projects. Programs, portfolios, goals, releases, resource plans, time cards, and rate cards are not artifacts created from a demand, and ideas flow the other way: an idea can be converted into a demand, not created from one.