Background: Charlie's take on app vs. proj portfolio management.
Like this article by Ephraim Schwartz at Infoworld. He discusses Niku (with their new Clarity suite) as an example of top-down IT project portfolio management, while BluePhoenix is bottom-up. (Hadn't heard of BluePhoenix before.)
The top-down versus bottom-up orientation is familiar; I baked it into my covergence model:
.
HAL, Troux, Relicore, and Cast all also play in the bottom-up space. One quibble: the article seems to conflate project portfolio management with IT portfolio management; as I argue here they are really two separate things.
Homage to the metadata origins of this weblog: Judging by their web site, Blue Phoenix -- with its emphasis on legacy systems re-engineering, and focus on OS/390 -- has major overlaps with territory the CA-Advantage repository has covered for the better part of two decades (tracing through the Brownstone/Reltech lineage.) The mainframe scanners for Advantage are very well respected and mature. There is nothing new under the sun. However, Blue Phoenix moves forward by focusing on platform modernization as well as discovery.
-ctb
