Services & Portfolios
See delivery the way your organization actually works.
Bring teams working across Jira, Azure DevOps and other data sources into the services and portfolios they deliver, without reorganizing the tools underneath them.
- Payments API
Jira - Payments WebJira
- Payments Mobile
Azure DevOps
- Mobile AppAzure DevOps
- Mobile PlatformJira
The disconnect
Your tools know about teams. Leadership thinks in services.
Delivery tools
- Jira board
- Jira board
- Azure DevOps project
- Jira board
CSV/imported data
How the business sees it
- Digital Payments
- Mobile Banking
- Customer Onboarding
Nave gives you a layer above the tools, so you can model delivery around the services the organization actually runs.
Model the service
One service, every team contributing to it.
Select the team dashboards that contribute to a service. Nave combines them in one value stream, with cycle time and throughput, percentile cycle time, and trends across the work.
Keep team context
Keep each team’s view without flattening the service.
The combined view does not erase how each team works. Apply filters for each team, including queue states, issue types and labels used as classes of service, while reading performance across the service.
Work across tools
Jira and Azure DevOps don’t have to live in separate reporting worlds.
Bring teams together across transformations, migrations, acquisitions or uneven tool adoption. A value stream can combine team dashboards from any tool Nave connects to.
See all integrationsDigital Payments
- Payments APIJira
- Payments WebJira
- Payments MobileAzure DevOps
One value stream
Define the structure
Build the hierarchy around your operating model.
Start with the team dashboards you already have, then organize them around the services and portfolios the business runs.
Select the teams
Choose the team dashboards that contribute to the service, including dashboards connected from different delivery tools.
Create the value stream
Name the value stream and add the selected dashboards. Edit it later when teams join, leave or move.
Build the portfolio
Group related value streams into a portfolio that reflects how leadership manages delivery across the organization.
Organization view
You’ve defined the delivery system. Now read its performance.
Executive Dashboards use your Services & Portfolios structure to show how delivery is changing across the organization.
Explore Executive DashboardsFaq
Questions about services and portfolios
Team dashboards roll up into value streams, which represent the services your organization delivers. Value streams then roll up into portfolios. This lets you preserve team-level detail while reading performance at the service and portfolio levels.
Yes. A value stream can include team dashboards from any tool Nave connects to, including Jira and Azure DevOps.
Yes. Building a value stream does not replace the team dashboards. Each remains available with its charts, Process Improvement and AI Investigator. In the combined dashboard, you can filter each team by its own queue states, issue types or labels used as classes of service.
No. Portfolios are the highest level in this structure. They combine related value streams so you can read delivery performance across a broader part of the organization.
Yes. Edit the value stream to change which team dashboards it includes. This lets the structure follow the service as teams join, leave or move.
Access is set per user. Give a user full access to all value streams, view-only access to all, or access only to specific value streams. The same options apply to portfolios.
Yes. Nave has one price, with no plans or add-ons. Every board includes every feature and unlimited users.