CIS-SPM Study Guide

Certified Implementation Specialist: Strategic Portfolio Management

Trademark disclaimer: ServiceNow, Strategic Portfolio Management (SPM), IT Business Management (ITBM), and all related product and release names are trademarks of ServiceNow, Inc. This is an independent, original study aid and is not affiliated with, endorsed by, or sponsored by ServiceNow. All facts are paraphrased from publicly available official ServiceNow documentation; no copyrighted course material is reproduced.

How to use this guide

The CIS-SPM exam validates that you can configure, implement, and maintain the ServiceNow SPM application suite. The mainline exam is 60 questions / 90 minutes, multiple-choice (single answer) and multiple-select. SPM is the current name for what was historically called ITBM (IT Business Management) and, in the project layer, PPM (Project Portfolio Management). You will still see legacy "ITBM" labels in older tables, plugins, and ACLs.

WEIGHT WARNING: READ FIRST. Several domain weights in the source blueprint are flagged UNVERIFIED because the official ServiceNow University blueprint page is JavaScript-gated and the published percentages could not be machine-confirmed at the source. Treat the weights below as a planning approximation, not gospel. Study every domain; do not skip a "small" domain on the assumption its weight is correct. The verified, official blueprint lives at the ServiceNow University CIS-SPM credential page: confirm current weights there before your exam.

Domains below are ordered by weight (highest first) per the working blueprint.

Domain: Idea & Demand Configuration (≈21%) [WEIGHT UNVERIFIED]

This is one of the two heaviest domains. It covers the front end of the SPM value stream: capturing raw ideas, turning the good ones into demands, and assessing/prioritizing demands before they become funded work.

Idea Management & the Idea Portal. The Idea Portal is the central, employee-facing place to submit, view, vote/comment on, and collaborate on ideas. Ideas move through Zurich Idea Portal states such as Submitted → Under Review → In Backlog → Planned → In Development → Completed, with Need more information, Unlikely to implement, Already exists, and Duplicate branches. A user with the idea_manager role evaluates submitted ideas. To accept a feasible idea, the idea manager sets it to In Backlog (this replaced the legacy Accepted state; there is no Accepted or Qualified idea state), then uses Create Task to convert it into a Demand, Project, Epic, Story, or SAFe item. The demand manager takes over once a demand exists. Ideas are stored and grouped in Idea modules (for example, one per product, department, or business unit) with idea categories kept as records in the Idea Category [im_category] table; there is no idea campaign feature. A duplicate idea is associated with the original and closed for comments and votes.

Demand Management. Demand Management captures, centralizes, and assesses both strategic and operational demands and provides a single place to manage all demand information. A demand is a formal proposal for work that has not yet been approved/funded.

Demand lifecycle / states. A demand progresses through Draft → Submitted → Screening → Qualified → Approved → Completed, and can also be Deferred or set to Incomplete. There is no Rejected demand state; a demand that does not move forward is deferred or closed, not deleted. Key behaviors to memorize:

Moving a demand to Screening sends assessments to the stakeholders when the Assessment Required field is set.
In the classic Demand Management UI the demand manager selects Qualify to move a demand to Qualified. In the Next Experience for Demand Management the state moves to Qualified automatically once the required assessments are submitted, and the demand manager can still set it manually (for example, when assessments are delayed or not required).
An approved demand can be converted into downstream work based on its Category and Type: a Project, Enhancement, Change, Defect, an Agile Development 2.0 Epic or Story, or EAP entities.
Zurich recommends the Next Experience for Demand Management (in Portfolio Planning Workspace or Strategic Planning Workspace) for new customers; the classic UI and Demand Workbench remain for existing customers.

Assessment & scoring. Demands are evaluated with question-driven assessments (the platform Assessment engine). Demand Management ships an assessment metric type named Demand with five default categories (Size, Strategic Alignment, Risk, ROI, Cost). Categories and metrics carry weights (a 1 to 10 weighting scale is recommended; the default weight is 10). The demand Score is calculated from the risk, value, and size attributes, which come from the assessment category results.

Demand Workbench. The Demand Workbench (classic) is the single-screen tool to assess and approve qualified demands and create projects, enhancements, changes, or defects. Its bubble chart plots risk (X axis), value (Y axis), and size (bubble), configurable in Workbench Config - Demand. Dragging a bubble changes the demand's risk or value; it does not rank demands. Relative ranking (Rank By Score or an edited Rank) is done in portfolio planning.

Configuration topics likely tested: idea states and Idea modules, idea categories, demand states and stage rules, the Demand assessment metric type and the Assessment Required field, idea conversion with Create Task and the data migrated from a demand to a project (fields, cost and benefit plans, budgets, RIDAC, resource assignments), demand workbench configuration, and roles (idea_admin, idea_manager, idea_manager_professional, it_demand_manager, it_demand_user).

Domain: Project Management Configuration (≈21%) [WEIGHT UNVERIFIED]

The other heaviest domain. This is PPM, the execution layer for funded work.

Project Workspace. The modern, configurable workspace that unifies planning, resourcing, financials, risk, and reporting for a project in one connected UI. Areas include the planning page (data grid and Gantt timeline), Resources, Financials, RIDAC (risks, issues, decisions, actions, change requests), and Status reports. Project Workspace has no board view of its own; boards come from Collaborative Work Management.

Work Breakdown Structure (WBS) & Planning Console. The Planning Console is the central interface giving the project manager a hierarchical view of the project: sub-projects and project tasks shown as a work breakdown structure (WBS), with a Gantt chart, milestones, dependencies/relations (e.g., finish-to-start), critical path, baselines, and rollup of dates/effort. Zurich documents the Planning Console as legacy; the Project Workspace planning page is the current experience. The Planning tab in Project Workspace brings WBS, Gantt, milestones, and task dependencies together.

Project methodology & states. Projects can run Waterfall, Agile, or Hybrid. Project states are the State field choices: Pending, Open, Work in Progress, Closed Complete, Closed Incomplete, Closed Skipped; the state rolls up from project tasks, and custom states are added per state type with dictionary overrides. Status report health (overall, schedule, cost, resources, scope) is shown in green, yellow, and red.

Status reports. Project managers publish periodic status reports capturing overall status, schedule/cost/scope/resource health, accomplishments, and upcoming work; newer releases offer AI-generated status report drafts. Status feeds portfolio dashboards.

Project tasks & scheduling. Tasks carry planned/actual start and end, % complete, planned duration, planned effort, assignment, and dependency relations (Finish to Start and others, with lag). Planned duration and planned effort are separate estimates; parent planned effort becomes read-only and rolls up from child tasks, and percent complete is entered or rolled up from child tasks (time cards update actual effort, not percent complete). The Time constraint field offers only Start ASAP, Start on specific date, Start no earlier than, and Start no later than; there are no finish constraints and no backward scheduling. A project uses Automatic or Manual calculation, and Start ASAP tasks are scheduled from the project's constraint date (its planned start, changed with Move Project).

Configuration topics likely tested: project templates, the planning console (rescheduling, relations, top-down vs. bottom-up tasking), project state flows, status report cadence/configuration, copying/templating projects, Project Workspace configuration, and conversion from demand to project.

Domain: SPM Applications Overview (≈20%) [WEIGHT UNVERIFIED]

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.

Domain: Resource Management Configuration (≈17%) [WEIGHT UNVERIFIED]

Balances the supply of people against the demand for work.

Resource plans vs. resource assignments. Historically work was resourced via resource plans (request a role/group/person for a period and effort). Starting in Utah and maturing through Vancouver/Washington, ServiceNow introduced resource assignments (Resource Management Workspace) as the modern way to manage resourcing: attribute based, with a heat-map view of availability by allocation level. Zurich states that resource plans will no longer be available for new customers in future releases. Know both models; the exam spans releases.

Allocations. A classic resource plan moves Planning → Requested → Confirmed → Allocated → Completed (or Rejected, Canceled). Confirming a plan creates soft allocations (temporary bookings with no calendar events); allocating it converts them to hard allocations, after which the resource is not available for other plans (Confirm and Allocate does both). Requests can be for a group, a user in a group, a user, or a role. The allocation spread is Even, Front load, or Smart Even Load. Actuals come from approved time cards.

Capacity planning. Capacity is a resource's available hours and is derived from the user's schedule, not from FTE (FTE only converts FTE requests into planned hours). Operational resource assignments for time off, training, or meetings reduce the capacity left for project work. Availability is capacity minus soft and hard allocations; forecasted utilization is (allocated + confirmed hours) / capacity and committed utilization is allocated hours / capacity. Capacity planning balances supply vs. demand across a portfolio using planning attributes as the common currency. A single screen lists resource plans with capacity, availability, soft & hard allocations, actuals, and % utilization. Strategic capacity planning is enabled by installing the Portfolio/Strategic Planning Workspace (Project Workspace and Resource Management Workspace are required).

Configuration topics likely tested: resource definitions, user/group capacity & schedules, availability and time-off, confirming, allocating and rejecting resource plans, the classic Resource Workbench and Resource Management Workspace, planning attributes, and how time cards roll up to actuals.

Domain: SPM Financials Configuration (≈8%) [WEIGHT UNVERIFIED]

Financial planning across demands, projects, programs, and epics.

Cost plans. A cost plan estimates costs over fiscal periods, broken down by cost type/expense type (capex/opex, labor/non-labor). Total Planned Cost = sum of all cost plan line items. Labor costs can be generated automatically from resource assignments (rate × effort).

Benefit plans. A benefit plan captures expected and realized benefits over time, by category. Planned Benefit = sum of all benefit plan line items. Used for ROI/NPV-style comparison.

Budgets. A budget is money allocated to a demand/project for a fiscal period. The Flexible Budget Allocation capability (introduced ~Aug 2024 releases) lets portfolio managers approve budgets monthly, quarterly, or yearly, with detailed breakdowns by expense/cost type and a "Copy cost as budget" option to approve bottom-up from forecast.

Display modes & forecasting. SPM Financials display modes (e.g., Forecast mode) flex the view across budget, forecast, planned, and actual costs and show forward-looking spend by fiscal period.

Expense lines record actual costs (for example, labor from processed time cards or purchased items) and roll up to total actual cost when processed; planned costs live in cost plans.

Configuration topics likely tested: fiscal period/calendar setup, cost/benefit plan templates and breakdowns, labor rate cards and rate models, functional currency and project currency, budget approval workflow, actual cost capture, and the new Financials experience for projects/demands/epics.

Domain: Timecard Management Configuration (≈5%) [WEIGHT UNVERIFIED]

Time Card Management captures time worked against tasks, projects, demands, problems, or other configurable targets in SPM and ITSM. Know the structure: a Time Sheet (weekly) contains Time Cards, and each time card holds hours by day. Time sheets are always weekly; the time sheet policy only sets the day the week starts. Time can be entered via the time sheet portal/UI and mobile time cards.

Approval & rollup. Time card states are Pending, Submitted, Approved, Rejected, Processed (approved with an expense line), and Recalled. Approved hours become actual effort, and processed time cards create expense lines (actual cost) that roll up to tasks and feed resource actuals and financials. Time sheet policies set the week start day, maximum hours per day and week, automatic time card creation, recall, rate types, and the Project time approver (Auto, Project Manager, User Manager, Both, None) and Non-project time approver. Each user has one policy (assigned through the policy's Users list); the default policy covers everyone else. What users log time against comes from their tasks and the time card categories (Admin, Meeting, Training, and others, plus project time categories), not from the policy.

Domain: Portfolio Planning Workspace (≈3%) [WEIGHT UNVERIFIED]

The Portfolio Planning Workspace (and the broader Strategic Planning Workspace, SPW) is an intuitive workspace to prioritize, roadmap, and track work. It lets planners prioritize demands and projects, visualize them on a roadmap/timeline, run scenario planning ("what-if" funding/sequencing), and connect strategy to execution via goals, OKRs, and targets. It is the planning hub that ties Strategic Planning → Portfolio Planning → execution. Capacity planning benefits depend on this workspace being installed.

Domain: Performance Analytics, Reporting & Dashboards (≈2%) [WEIGHT UNVERIFIED]

SPM ships Performance Analytics (PA) content, dashboards, and reports for portfolios, projects, resources, and financials. Know the difference: Reporting = point-in-time data from tables; Performance Analytics = time-series, snapshot-based KPIs and scorecards showing trends. SPM dashboards surface portfolio health, demand pipeline, resource utilization, and financial variance. Indicators/breakdowns and data collection jobs drive PA.

Domain: SPM Implementation Overview (≈2%) [WEIGHT UNVERIFIED]

High-level implementation lifecycle and methodology: scoping the SPM rollout, the recommended crawl-walk-run adoption (e.g., start with Project/Demand, then Resource, then Financials, then Agile/Strategic Planning), plugin/store-app activation order and dependencies, persona/role setup, and Now Create implementation guidance. Understand prerequisites (e.g., installing Project Workspace and Resource Management Workspace before strategic capacity planning).

Domain: Release Mgmt & Digital Portfolio Mgmt (≈1%) [WEIGHT UNVERIFIED]

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.

Fast-recall cheat list

ITBM = SPM (rename announced 2022); project layer historically PPM. Legacy "ITBM"/pm_/dmn_ labels still appear.
Exam: 60 questions, 90 minutes, single + multi-select.
Value stream: Strategic/Portfolio Planning → Idea → Demand → Project/Agile → Resource & Financial → Delivery → PA.
Idea Portal = submit, vote, and comment on ideas; accepting an idea sets it to In Backlog, then Create Task converts it to a Demand (or project, epic, story).
Demand states: Draft → Submitted → Screening → Qualified → Approved → Completed (plus Deferred and Incomplete).
Screening sends assessments to stakeholders (Assessment Required); classic UI: demand manager selects Qualify; Next Experience: auto Qualified when required assessments are in.
Approved demand converts (by Category and Type) to Project / Enhancement / Change / Defect / Epic or Story / EAP entities.
Demand Workbench (classic) = bubble chart of qualified demands (risk, value, size); ranking is done in portfolio planning.
Project Workspace unifies planning, resourcing, financials, risk, reporting.
Planning Console (legacy) = WBS + Gantt + milestones + dependencies + critical path. Time constraints: Start ASAP / on specific date / no earlier than / no later than.
Project states: Pending, Open, Work in Progress, Closed Complete / Incomplete / Skipped; health = green, yellow, red; status reports (AI-assisted) feed dashboards.
Resource plans (legacy) vs. resource assignments (Utah→Washington, modern).
Allocations: Confirmed plan = soft allocations; Allocated plan = hard allocations; requests by group, user, or role.
Capacity = available hours from the user's schedule (not FTE); capacity planning balances supply vs. demand via planning attributes.
Cost plan → Total Planned Cost; Benefit plan → Planned Benefit; Budget = allocated money per fiscal period.
Flexible Budget Allocation: approve monthly/quarterly/yearly; "Copy cost as budget."
Financials display modes: budget / forecast / planned / actual.
Time Sheet (always weekly) → Time Cards (hours/day) → approved → actual effort; processed → expense lines. One time sheet policy per user.
Portfolio/Strategic Planning Workspace: prioritize, roadmap, scenario planning, goals/OKRs/targets.
Agile Development 2.0 = scrum Agile board; SAFe = separate Essential/Portfolio SAFe apps; EAP in SPW; scrum program planning board + release dashboard for releases.
PA = time-series snapshot KPIs/scorecards; Reporting = point-in-time.
Digital Portfolio Management = solutions (services, offerings, business apps, service instances) across plan, build, run. Enterprise Architecture (formerly APM) = application rationalization.
Data spine: Idea → Demand → Investment (Cost Plans + Benefit Plans + Budget); Portfolio ⊃ Programs, Projects, Demands.

Remember: domain weights here are an UNVERIFIED planning approximation. Confirm current percentages on the official ServiceNow University CIS-SPM blueprint before exam day.