Engagement Methodology and Project Planning
About 10% of the CIS-CSM exam — see all 4 domains.
ServiceNow expects implementers to follow a prescribed delivery methodology and manage scope professionally.
- Now Create (the ServiceNow implementation methodology, formerly the ServiceNow Implementation Methodology / SIM) breaks an engagement into phases — commonly Initiate → Plan → Design (workshops) → Build/Configure → Test → Deploy → Operate (and Optimize) — backed by reusable assets, accelerators, and leading practices.
- Statement of Work (SOW) — formally defines scope, deliverables, timeline, and boundaries the team commits to.
- Design workshops — validate business requirements and confirm the future-state process with stakeholders before building. Requirements become user stories.
- Scope / change control — any out-of-scope request must be impact-assessed (effort, timeline, risk, regression) and routed through the change control process for sponsor decision. Never silently absorb work (scope creep) or refuse without explanation.
- Leading practices to reduce risk — engage stakeholders early; use out-of-box first before customizing; phase the rollout (MVP then iterate); validate with UAT; plan data migration and go-live readiness.
Sample questions from this domain
Three of the 30 in this domain, with the reasoning. The full set is in the question bank.
During a ServiceNow CSM implementation, which methodology does ServiceNow recommend partners and customers follow to deliver the project in structured, value-driven phases?
- A. SAFe Agile Release Train
- B. ServiceNow Now Create / Implementation (NowCreate) methodology ✓
- C. PRINCE2 stage gates
- D. ITIL v4 Service Value System
Why: ServiceNow's prescribed delivery methodology (Now Create) breaks engagements into the phases Initiate, Plan, Execute, Deliver, and Close, with reusable assets. ITIL v4, SAFe, and PRINCE2 are general frameworks, not ServiceNow's implementation methodology.
In a CSM engagement, which document captures the agreed-upon scope, deliverables, and boundaries that the implementation team commits to deliver?
- A. The Case form layout
- B. The Service Level Agreement (SLA) definition
- C. The Statement of Work (SOW) ✓
- D. The Knowledge Base article
Why: The Statement of Work formally defines project scope, deliverables, timeline, and boundaries. A KB article is end-user documentation, an SLA definition governs response/resolution timing for cases, and a case form layout is a configuration artifact—none define overall engagement scope.
A customer requests a feature during the Build phase that was not included in the approved Statement of Work. What is the appropriate first action for the implementation lead?
- A. Cancel the current sprint and replan the entire project
- B. Silently defer it to the Operate phase without telling anyone
- C. Implement it immediately to keep the customer satisfied
- D. Raise it through the project's scope change / change control process ✓
Why: Out-of-scope requests must go through the formal change/scope control process so impact on cost, timeline, and resources is assessed and approved. Implementing immediately causes scope creep, silent deferral lacks transparency, and cancelling the sprint is disproportionate.