Decisions need evidence.
AIVANA Decision Intelligence
Identify business risks. Check sources. Trace decisions together. In the context of your work with Azure DevOps Services.
Development preview · Arrange team service separately
Two statements. One conflict.
Supported interface clauses conflict. Both original statements provide the starting point for review.
One team. Seven perspectives.
From the current sprint to a historical balance of remaining scope: configurable dashboard widgets bring the right question into your team routine.
A decision with a history.
Understand sources
Explicitly start an analysis in Boards → AIVANA. Trace release risks, supported interface conflicts and acceptance gaps back to their sources.
Weigh the options
Review business changes and their impact. Evidence-linked draft options support the discussion; accountable people decide.
Keep a shared record
In the activated team service, trace decisions with their author, timestamp and source snapshot. Project roles govern access; JSON export supports handover.
Start with your next real question.
For project leads, product owners, business analysts and delivery teams with complex business interfaces. Together, we discuss your use case and potential preview access.
Azure DevOps Services extension
Development/preview version. Check installation and organization approval in the Marketplace. We agree access, project scope and terms for the shared team service with you.
Marketplace: development versionClear questions. Clear boundaries.
Does the extension automatically approve releases?
No. It supports reviewing and documenting decisions. There are no automatic release approvals or writes to Azure work items. AI is disabled and excluded from this edition.
Which permissions apply?
Live access requires the installed extension and current Azure permissions. The shared team service checks identity and project access with every request. Additional roles are explicitly granted per project and cover all source snapshots stored there, rather than individual Azure areas.
What is stored for the team?
The separately activated team service stores shared history and source snapshots with project roles and JSON export. Local analyses and widgets can be used separately. Changed sources need to be reviewed again in a new analysis.
How far does an analysis reach?
An explicitly started project analysis covers up to 5,000 work items. Dependencies relate to loaded items. Fortschritts-Realität compares from sprint start or a selected timestamp, looking back up to 90 days. Missing history is disclosed; incomplete data does not produce complete totals.
Can I already buy the product publicly?
The linked Marketplace listing is the development version. We discuss preview access, project scope and potential trial terms directly. A trial is activated by the operator and does not automatically convert into a paid subscription.