There are two ways to do what you are talking about, and it depends on whether you want to create reports or if you are talking about a breakdown structure.
If you need a work breakdown structure, I would recommend changing your process so that you don't, or processing it exclusively at the PMO level. Enshrining the dependencies in the instrument at something lower than in Portfolio tells me that you can create solutions for effects, and not get from the route the cause of particle dysfunction, which is fixed in your culture. [PreachMode = false] However ...
# 1 - Reporting
You can create a report services report that presents data from the data warehouse and cube to create the desired view.
This will give you read-only presentation of data and lead to the least invasive dysfunctions.
# 2 - MS Project
You can use MS Project to load Parent / Child and Network elements and maintain a Gant chart with dependencies stored in TFS.
- I could not find a good link, but there is documentation on MSDN
This will give you an interactive view of the data in the online storage, but will lead to the most invasive dysfunctions.
# 3 - Project Server
If you are implementing something more than the Scaled Agile Framework , then you may need to use the Earned Value management to integrate Project Server as well as some portfolio management features.
I hope that you can find something suitable, and you will have the opportunity to explore the branching of your current process on the ability of your teams and organization to achieve any agility in the new normal modern application life cycle .
source share