http://blogs.msdn.com/anlynes/archive/tags/EA/default.aspxTags: EAen-AUCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/anlynes/archive/2006/12/13/application-portfolios.aspxWed, 13 Dec 2006 07:37:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:1271563anlynes1http://blogs.msdn.com/anlynes/comments/1271563.aspxhttp://blogs.msdn.com/anlynes/commentrss.aspx?PostID=1271563<P>Recently I joined a newly formed Enterprise Architecture team. I've never been in on the ground floor before, so it's an interesting experience. One thing that kept coming up in our planning discussions was a need to&nbsp;list/record&nbsp;the application assets we have, who owns them, their dependencies&nbsp;etc. We have a lot of products at Microsoft (and a lot of internal e-mails about them). Somewhere in amongst this, I was sure I had been told Microsoft had entered this space. It turns out we did in the form of <A class="" href="http://office.microsoft.com/en-us/portfolioserver/FX101674151033.aspx" mce_href="http://office.microsoft.com/en-us/portfolioserver/FX101674151033.aspx">Microsoft Office Project Portfolio Server</A>.</P> <P>Application Portfolio Management is a huge topic with widely varying opinions about what features are required in a tool. Side-stepping all of that, if some of the things I've listed above would be useful for you, why not have a look at Project Portfolio Server?</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1271563" width="1" height="1">EPMEA