SPM Implementation Overview
About 2% of the CIS-SPM exam — see all 10 domains.
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).
Sample questions from this domain
Three of the 6 in this domain, with the reasoning. The full set is in the question bank.
During a ServiceNow SPM implementation, which activity best aligns with the Now Create methodology phase that occurs before any configuration begins?
- A. Migrating historical time card data
- B. Activating the Agile Development plugin
- C. Defining the project's scope, stakeholders, and success criteria ✓
- D. Building cost plans for each project
Why: Now Create front-loads scoping and alignment, so defining scope, stakeholders, and success criteria precedes configuration. Cost plans, data migration, and plugin activation are downstream build/configure activities, not pre-configuration alignment work.
An implementation specialist needs to enable the core Strategic Portfolio Management capabilities (Project, Demand, Resource, and Portfolio management) on a new instance. What is the recommended approach?
- A. Activate the relevant SPM plugins/store applications, which install the baseline data model and modules ✓
- B. Clone a production instance that already has SPM
- C. Manually create each table and form from scratch
- D. Request ServiceNow Support to hard-code the applications
Why: SPM capabilities are delivered as plugins/store applications that install the baseline tables, modules, and configuration. Manually building tables, cloning production, or asking Support to hard-code are not the supported enablement path.
Which two considerations are most important when sequencing the activation of SPM applications during an implementation? (Choose two)
- A. Dependent applications (e.g., Project on top of Resource Management) should be activated in dependency order ✓
- B. Activation order has no functional impact
- C. Activating a plugin on production is irreversible, so plan and test in a sub-production instance first ✓
- D. All plugins must be activated simultaneously to avoid data loss
- E. Plugins can only be activated by ServiceNow Support tickets
Why: Application dependencies dictate activation order, and because plugin activation generally cannot be undone, you validate in a sub-production instance first. Simultaneous activation is not required (B), customers can self-activate most plugins (D), and order does matter (E).