Skip to main content

Verified program status for ServiceNow

Tarivra reads ServiceNow Agile Development and Change Management together, so a program's status reflects both the delivery work and the changes that reached production, including the incidents they caused.

Connecting ServiceNow

Your ServiceNow admin sets up an OAuth client for a dedicated integration user. There is no shared password.

  • Roles itil and scrum_user (scrum_admin only if Themes or Releases are programs)
  • OAuth scope limited to the Table API on the agile, change, incident and user tables Tarivra reads
  • No admin role

What becomes a program

A team adds the tarivra-program tag to the record its work rolls up to, usually an Epic. Its work is the stories that point to it.

  • An Epic, Theme, Release, Sprint or Product works, through the story's matching field
  • Needs the Agile Development 2.0 plugin
  • A RAG: Green, Amber or Red tag gives the declared status, credited to whoever added it

What Tarivra reads

Tarivra never reads source code, attachments or anything outside the projects, repositories and tables you grant.

  • Epics and stories: state, assigned to, due and end dates, story points and blocked flags
  • Change requests from the last 120 days: type, risk, approval, state, close code and planned dates
  • Incidents caused by those changes
  • Web links in other tools that name a ServiceNow story, for dependencies across tools

How the status is checked

Tarivra compares the status the team reports with what the work shows, runs these checks and scores how well the two agree.

  • Schedule
    Is the work finishing fast enough to make the target date?
  • Scope growth
    How much work was added after the start?
  • Throughput
    Is the team finishing work at a steady pace?
  • Overdue work
    How much is past its due date?
  • Blocked work
    How much is flagged or marked blocked?
  • Stale work
    Is in-progress work sitting untouched?
  • Change health
    Did recent ServiceNow changes fail or cause incidents?

Decisions that stick

An approved decision becomes a story linked to the program's record, with a correlation id so a retry finds the story it made. The decision closes in Tarivra when the story is complete.

This is the only thing Tarivra writes, and only if you allow it. Every decision is also kept in an audit log nobody can edit.

Questions

What is change health?

One of Tarivra's checks: how many of a program's recently closed changes failed or caused incidents, and whether high-risk changes are still waiting for approval. A program can report Green while its changes keep breaking production; change health shows it.

Do we need ServiceNow for delivery work too?

No. You can connect ServiceNow only for change and incident data while delivery work stays in Jira, Azure DevOps, GitHub or GitLab.

Does Tarivra need the admin role?

No. An integration user with itil and scrum_user, through OAuth limited to the tables Tarivra reads, is enough.