At last Thursday's OSLC Community Webcast Series presentation I was introduced to a new company focusing on Strategic Planning for IT: Corso.
I found the presentation to be very interesting as it served as a good introduction to Strategic Planning, its challenges, and how OSLC helps simplify Corso's solution.
Since the webcast was not recorded, I thought I would share some of the notes I took during the presentation both to encourage you to take a look at the presentation slides, but also to try to fill them in as was done so well by the speakers (Jamie Knowles and Martin Owen).
Here are my notes:
- OSLC and Jazz play a role in connecting the Strategic Planning Platform (SPP) to the common tools used in IT organizations.
- In order to do strategic planning, you need to get lots of real information that is held in lots of different places.
- In the old days, you’d have to import everything from those tools into the SPP repository.
- With OSLC, you don’t have to import, just link.
- Also, you don’t have to write an integration for each tool that does “requirements”, for example, but have a common integration for all “requirements” products.
- “We’re no longer really referring to tools, we’re referring to a set of capabilities.”
- Standard interfaces and standard resource descriptions mean that different products of different versions can interoperate without issue. Thus both end users and third party vendors can build integrated solutions containing multi vendor solutions with minimal risk and cost.
- Focus of SPP – do the right things, at the right time.
- Once you have triaged & prioritized your ideas, you can assess their affects on the Enterprise Architecture (EA); using SPP, we don’t just produce a set of EA changes, but Business Proposals.
- A benefit: all the projects that come out the end, we have full traceability to where the idea came from, and the analysis that went into the project being chartered.
I think its wonderful that OSLC has simplified the connections and interactions between Corso's SPP and products implementing ALM specifications, but looking at the complete environment in which SPP works, Corso must have implemented many "traditional" integrations too. Some might not be common enough, or well enough defined, to be good candidates for an OSLC specification, but some may be. With so many integration points for Corso's SPP, alone, there must be dozens more integration points across the "World of Software" that would be good candidates for a little OSLC love!
For a little diversion, I’ve started a thread in the forums for your thoughts: what non-ALM integrations do you think would benefit from an OSLC specification?
Maybe Jamie and Martin are already aware of some integration they wish was covered by an OSLC specification?
Don't forget to join us again next Thursday, March 1, for another webcast: Announcing the Rational OSLC Adapter for Atlassian JIRA