Enterprise Portfolio - Connect demand intake to delivery across multiple portfolio teams

So here I am in one of my demo environments in Craft IO, I'm in the Orbit Portfolio.

The Enterprise portfolio.

We can see from a green banner and we can open this up and we can see in the navigation all of the portfolios that live within this specific enterprise portfolio.

In this example, we have the Atlas portfolio with a number of different workspaces.

We have the Global Feedback Triage workspace, living in its own feedback portfolio.

And we have the ACME portfolio.

And the aim here is that we have multiple different workspaces and portfolios, or all now rolling up to one super portfolio structure where all of the different banners can now roll up into.

it means that each of those individual portfolios and workspaces can continue to be managed by different parts of the organization.

So everyone has autonomy over their own ways of working.

But it can all roll up into a single view.

We can see in this specific structure, we.

We can see initiatives and epics from multiple different portfolios in addition to a super initiative structure which lives in this specific enterprise portfolio.

So now let's jump into one of our timeline roadmaps and we can see the piece of the puzzle that solves the problem we have with intake.

So here I am in a timeline view in this enterprise portfolio structure.

and as per the traditional timeline views in your workspaces and portfolios.

We do have access to dependencies, as you'll see from these lines.

Scroll all the way to the bottom and we can see the feedback portfolio.

We're now able to group our items by portfolio, as you can see in the swimlane structure, now unlocked at this enterprise portfolio level.

So if we scroll to this original item, we can see that this item was the original piece of intake.

We can open it up and see a bit more information, the original request that came through, and also a bit of context with a link back to that original feedback item.

So this was created as a piece of intake, and once it went through that demand advisory, it was turned into a piece of work downstream.

And this may have existed across multiple different portfolios or workspaces.

So now visually in the timeline view, you can see dependencies between those initial pieces of intake and the pieces of work that they eventually become.

This means there's a single connected thread from the moment it was raised in the techintake feedback portal to the teams who are actually delivering it.

And, instead of that link getting lost the moment it left the triage workspace, we now have visuals between the various portfolios.

and the autonomy will stay where it belongs.

The new thing is that intake delivery and everything in between can now be seen and traced in a single view at the enterprise portfolio level.

If you have any questions, please reach out to your craft IO customer success representative.

Thank you for watching and happy crafting.