This is a great article that brings up some issues that can prevent the CMO and CIO from working effectively together and aligning their decisions with the enterprise’s business objectives, instead of their own departments.
This is also an area where IBM Rational can help, in facilitating collaboration between these two, sometimes silo’ed, entities, especially where software and system intensive solutions are at play.
IBM Rational’s tools for product portfolio management can help manage the input from both the CMO and CIO teams to the definition of the products provided by the enterprise. Each division provides its needs, its objectives, and its desired outcomes, and IBM Rational Focal Point can help blend all of this and keep it aligned with the overall division and enterprise business objectives. Each product (or project) can then be evaluated against these business objectives and scheduled accordingly.
Further integration between the product portfolio tools and IBM Rational’s collaborative lifecycle management platform then ensures that the software and system requirements can be traced to the implementation and deployment of the software/systems products.
Yes, this is a simplified view of the whole thing, but it can and has been done in the past!
Here are two great videos about sharing and, by extension, collaboration:
I do believe that sharing knowledge is important. Within IBM (where I’m employed), I do use many of the tools that are provided us to ensure that this is done – from internal implementations of IBM Connections and Rational Asset Manager to wikis and shared project storage area. I will, however, be the first to state that I could do better.
I was, however, wondering… Does using blogs, twitter, Connections, etc. to convey this message just panders to the converted? Are the people already doing this not the ones who would be reading those media?
IBM is still serious about dealing with all aspects of systems development. In the past, this was mainly seen as developing embedded software. More recently, with the rise in popularity of SysML, there have been added capabilities to support systems engineers’ needs for architecture modeling and development tooling. Now, IBM is taking the rest of the tools into consideration by attaching systems development to the Jazz platform: