Skip to main content

ServiceNow SPM status reporting: making health reflect the work

ServiceNow Strategic Portfolio Management (SPM) gives every project a status report with overall health and a few health indicators. They are only as accurate as the last person who updated them. This guide shows how to ground SPM status in the work ServiceNow already records.

By the Tarivra team · · 7 min read

How status works in SPM today

In SPM, a project manager publishes a status report for the project: an overall health, usually backed by indicators such as schedule, cost, resources and scope, plus comments. Portfolio and executive views roll those reports up.

The indicators are a judgment set by a person. The work itself, the project tasks, agile stories, change requests and incidents in the same instance, does not change them. That is why a project can show Green in the portfolio view while its stories have stalled.

The evidence ServiceNow already has

Most ServiceNow instances already hold everything needed to check a project's health:

  • Project tasks and agile stories, with their state, assignee, planned dates and when they last changed.
  • Epics and releases that group the work under a project or program.
  • Change requests linked to the work, with whether they succeeded, failed or were backed out.
  • Incidents caused by those changes.
  • The history of planned end dates, so you can see how often a date has moved.

Five checks to run against SPM status

Schedule

At the pace stories and tasks are closing, will the open work finish by the planned end date?

How to check:
Count work closed per week for the last six to eight weeks and compare the open work with the weeks left.
Red flag:
More weeks of work than weeks on the plan, under a Green schedule indicator.

Scope

How much work has been added since the project baseline?

How to check:
Count stories and tasks created after the baseline date as a share of the total.
Red flag:
Scope up by a fifth or more with no change to the plan.

Stuck work

How much of the open work is blocked, overdue or untouched?

How to check:
Count open items marked blocked, past their planned end, or not updated in 14 days.
Red flag:
Stuck work above a quarter of what is open.

Change health

Did the project's recent changes go in cleanly?

How to check:
Look at change requests linked to the project in the last 30 days: failed, backed out or with caused-by incidents.
Red flag:
Any failed change or a caused-by incident while health shows Green.

Date history

Has the planned end date moved, and how often?

How to check:
Compare the current planned end date with the baseline and earlier status reports.
Red flag:
Two or more moves while the status stayed Green.

Putting it into practice

  • Build a report per check on the task, story and change request tables, filtered to the projects in the portfolio.
  • Put the reported overall health beside the result of the checks on one dashboard.
  • In the portfolio review, discuss only the projects where the two disagree.
  • Record each decision from the review with an owner and a due date, as a task on the project, and check it the next week.
  • Review the thresholds once a quarter with the project managers who use them.

None of this replaces the project manager's judgment. It gives that judgment something to be checked against, and makes the conversation about facts.

When not everything is in ServiceNow

Many organizations run IT changes in ServiceNow while engineering teams plan in Jira, Azure DevOps, GitHub or GitLab. Then the project in SPM shows only part of the work. Use the same checks in every tool, map each tool's states to To do, In progress and Done, and link related items across tools, so a slip on one side is visible on the other.

Where Tarivra fits

Tarivra runs these checks continuously. It reads ServiceNow epics, stories, change requests and the incidents they caused, alongside Jira, Azure DevOps, GitHub and GitLab, compares the result with the status each program reports, and writes leadership decisions back to ServiceNow as stories that close when the work is done.

Questions

Does ServiceNow SPM calculate project health automatically?

Project health indicators in SPM are usually set by the project manager in the status report. The work records in the instance can be used to check them, but they do not change the indicators on their own.

Which ServiceNow records show whether a project is on track?

Project tasks and agile stories (state, planned dates, last update), change requests linked to the work (successful, failed or backed out) and incidents caused by those changes.

Can I check SPM status without buying another tool?

Yes. Reports on the task, story and change request tables cover the checks in this guide. The work is keeping them current and consistent across many projects and tools.