SERVICENOW · SPM

Strategic Portfolio Management, sized to what your organisation will actually maintain

SPM — the module ServiceNow used to call ITBM — fails more often on adoption than on configuration. Resource management needs timesheets. Portfolio reporting needs someone to keep demand records current. The implementation question is which of those disciplines your organisation will genuinely sustain.

You’ll speak to a certified consultant, not a salesperson.

ITSMITOM & CMDBDiscoveryService MappingEvent ManagementCSMSecOpsVulnerability ResponseSPMIntegrationsUpgrades

WHAT IT COVERS

SPM in practice

Demand Management

A single intake for ideas, requests and projects, with enough scoring to make prioritisation defensible.

Project & Portfolio

Planning, milestones, financials and status reporting, with portfolio views that a steering committee will actually read.

Resource Management

Capacity planning and allocation — powerful, and entirely dependent on people recording time honestly.

Agile Development

Stories, sprints and boards for teams that work that way, connected to the same demand pipeline.

Application Portfolio Management

What you run, what it costs, what it depends on, and what should be retired — built on the CMDB.

Financial planning

Budgets, forecasts and actuals against portfolios, at whatever granularity your finance function can supply.

WHERE IT GOES WRONG

Four ways SPM implementations disappoint

Resource management was switched on without timesheets

Capacity planning is arithmetic on data nobody entered. Either commit to time recording or scope resource management out — half-measures produce confident, wrong reports.

Demand and project intake were never merged

Two front doors means two priority lists and no portfolio view. The point of SPM is one pipeline.

APM without a CMDB

An application portfolio disconnected from the infrastructure it runs on cannot answer the dependency and cost questions that justified the project.

It was configured like Microsoft Project

Detailed Gantt planning that nobody updates. SPM earns its place through portfolio-level visibility, not task-level scheduling.

HOW WE APPROACH IT

What we do differently

Ask what you will actually sustain
We would rather implement demand and portfolio well than have resource management quietly abandoned after two quarters.
One intake, one pipeline
Every request enters the same way and gets scored the same way.
Report at the altitude decisions are made
Steering committees need portfolio health, not a task list.
Connect APM to the CMDB
So application cost and dependency questions have real answers.

Every engagement opens with the 30-day platform review. You keep the report and the plan whether or not you work with us.

QUESTIONS

Questions we get asked

Is SPM the same as ITBM?

Yes — ServiceNow renamed IT Business Management to Strategic Portfolio Management. If a supplier is still calling it ITBM, that tells you something about how current their practice is.

Do we need Agile Development if teams use Jira?

Usually not. Keeping delivery in Jira and portfolio in ServiceNow, with a defined integration point, is a legitimate and common architecture.

What is the minimum useful SPM implementation?

Demand intake plus portfolio reporting. That alone answers what are we doing and why, which is what most steering committees are missing.

Tell us what's not working

Thirty minutes, a certified consultant, and a straight answer about whether we can help with SPM. If we can’t, we’ll say so and point you somewhere better.

We reply within one working day. info@technowpartners.com · +32 488 981 604