Verified program status for Azure DevOps
Tarivra reads Azure Boards the way it is already set up: Epics, Features, stories and tasks, in any process. It checks each program's reported status against the work items below it and shows leaders where the two disagree.
Connecting Azure DevOps
Your admin creates a personal access token for a dedicated Azure DevOps user, scoped to your organization, with the shortest expiry you accept.
- Work Items: Read, plus Read & write only if decisions should be written back
- Project and Team: Read, so Tarivra can mirror who sees which project
- No Full access, Code, Build or Release scopes
What becomes a program
A team adds the tarivra-program tag to the work item its work rolls up to, usually an Epic. Every work item below it, Features, stories and tasks, counts as the program's work.
- Works with Agile, Scrum, CMMI and custom processes; each work item type's states map to the right category
- The tagged item gives the name, owner, target date and declared status
- Removing the tag stops new reads; the program's history stays
What Tarivra reads
Tarivra never reads source code, attachments or anything outside the projects, repositories and tables you grant.
- State and state history from the work item revisions
- Assigned to, target and due dates, and story points, effort or size
- Blocked flags and tags
- Parent and child links, predecessor and successor links, and web links to other tools marked blocked by or blocks
- When each work item was created, so work added after the start shows as scope growth
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.
- ScheduleIs the work finishing fast enough to make the target date?
- Scope growthHow much work was added after the start?
- ThroughputIs the team finishing work at a steady pace?
- Overdue workHow much is past its due date?
- Blocked workHow much is flagged or marked blocked?
- Stale workIs in-progress work sitting untouched?
Connect ServiceNow as well to add change health: whether recent changes failed or caused incidents.
Decisions that stick
An approved decision becomes a Task under the program's Epic, with its due date, assigned to the action owner when Azure DevOps resolves exactly one person. The decision closes in Tarivra when the Task is done.
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
Does Tarivra work with Azure DevOps Server?
Tarivra connects to Azure DevOps Services (dev.azure.com) today. If you run Azure DevOps Server on your own network, tell us when you request a demo.
We use a custom process. Will the states map?
Yes. Tarivra reads each work item type's states once, maps them to To do, In progress and Done by their category, and your admin can adjust any mapping.
Does it read our repositories or pipelines?
No. The token needs work item and project access only, and Tarivra never reads code, builds or releases.