Project and Portfolio Hierarchies Demystified

Document ID : KB000047563
Last Modified Date : 14/02/2018
Show Technical Document Details

Summary

Time and again, the confusion between the project hierarchy and the portfolio hierarchy has caused trouble that has impaired the growth of individual teams into a cohesive development organization. Not just in muddying the data but in hampering Agile maturation and growth in companies.

Issue

It?s time to clear this up using a few visualizations that have had great success when shared and explained to our users.

First, understand that the Project Hierarchy has absolutely nothing to do with a project in the traditional sense; this is not to reflect a period of time for development.

The Project Hierarchy is actually there to represent your organization and its various development streams: permanence over temporary.

The Portfolio Hierarchy is there to reflect the temporary development efforts identified by the business as key strategies lasting anywhere from 5 years to 1 month.



?

Cause

The best way to understand this is visually

?

When laid on it?s back:

aws-increments.png

?

With this I begin to understand that my hierarchies should look something like the following. ?This example is of an Online Store:

And the Portfolio Hierarchy, something like this:


If you would like additional information or advice on how to best set up your Project or Portfolio hierarchies just reach out to the Customer Success Team to hear back from your Customer Success Manager:?Team-AgileBU-CustomerSuccess-NA@ca.com