Enterprise Portfolio Types

Sandra Clendon
Mega Guru

Most of the DPM resources talk about service portfolios, but if you install the Enterprise Portfolio plug-in you can also create Business Application and Application Service portfolios.

Ideally, of course, you wouldn't have to do this and could just set up Enterprise Portfolios and include business applications, business services, technical services AND applications services, and I assume that will be a later development.  For now we are looking to create some Service Portfolios and replicate the structure for our product owners as Business Application Portfolios (Enterprise Portfolio - type = Business Application).

My question is this.  What is the use case for application service portfolios?  Which personas are these designed to support?

Also - could someone please set up a hashtag for DPM?

1 ACCEPTED SOLUTION

Sandra Clendon
Mega Guru

Here is what we ended up using each type of portfolio for:

- Business Application Portfolios for Product Owner visibility - they can see what is happening in their portfolio.  While we didn't have SPM, we did have Agile Development so by naming the Agile Products exactly the same as the Business Application, Product Owners were able to see all of the Agile related widgets, in addition to the performance widgets.

- Service Portfolios for Service Owner visibility.  Sometimes it is the same person (a product owner responsible for services associated with their product portfolio), but it is a different use case.

- Application Service Portfolios for Incident Manager visibility.  We started with the 5 most critical business applications and put the Production instances of those applications into an Application Service Portfolio so that the Incident Manager could more easily view, respond to, and report on that top 5.

View solution in original post

3 REPLIES 3

jaguthrie
Tera Contributor

Were you able to find anything out about this?  I am looking for the same answer.  What is the difference between the three portfolio types and when should we be using one vs the other?

Sandra Clendon
Mega Guru

Here is what we ended up using each type of portfolio for:

- Business Application Portfolios for Product Owner visibility - they can see what is happening in their portfolio.  While we didn't have SPM, we did have Agile Development so by naming the Agile Products exactly the same as the Business Application, Product Owners were able to see all of the Agile related widgets, in addition to the performance widgets.

- Service Portfolios for Service Owner visibility.  Sometimes it is the same person (a product owner responsible for services associated with their product portfolio), but it is a different use case.

- Application Service Portfolios for Incident Manager visibility.  We started with the 5 most critical business applications and put the Production instances of those applications into an Application Service Portfolio so that the Incident Manager could more easily view, respond to, and report on that top 5.

jaguthrie
Tera Contributor

Did a bit more digging and I did at least put this together which does help a little bit.  

jaguthrie_0-1721678419679.png