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 five phases, Initiate → Plan → Execute → Deliver → Close, 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. The Scaled Agile Framework (SAFe) with Agile Release Trains
- B. ServiceNow Now Create / Implementation (NowCreate) methodology ✓
- C. PRINCE2, managed through formal stage gates
- D. ITIL 4, aligned to the service value system
Why: Now Create is ServiceNow's prescribed delivery methodology: it breaks engagements into the phases Initiate, Plan, Execute, Deliver and Close, with reusable assets for each. SAFe with Agile Release Trains, PRINCE2 with stage gates and the ITIL 4 service value system are general industry frameworks; teams may borrow from them, but none is 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 RACI responsibility matrix
- B. The user acceptance test plan
- C. The Statement of Work (SOW) ✓
- D. The project RAID log
Why: The Statement of Work formally defines the project scope, deliverables, timeline and boundaries the team commits to. The RACI matrix says who is responsible, accountable, consulted and informed, not what is delivered. The user acceptance test plan describes how delivered functionality is validated. The RAID log tracks risks, assumptions, issues and dependencies during the project.
A customer requests a feature during the Execute (build) phase that was not included in the approved Statement of Work. What is the appropriate first action for the implementation lead?
- A. Add it to the current sprint because the Product Owner agreed verbally
- B. Log it as a defect so it can be fixed without a change request
- C. Defer it to the Close phase and build it during hypercare
- D. Raise it through the project's scope change / change control process ✓
Why: Out-of-scope requests go through the formal scope change (change control) process so the impact on cost, timeline and resources is assessed and approved by the right people. Adding it to the sprint on a verbal agreement is scope creep that bypasses that assessment. Logging it as a defect misrepresents new scope as a fix to agreed scope. Deferring it into hypercare is itself an unassessed scope decision, and hypercare is for stabilizing what went live, not building new features.