News Stay informed about the latest enterprise technology news and product updates.

More on Office 2010 timeline

It looks like Office 2010 is on track for its first-half of 2010 delivery. According to documents shared with some TAP participants, milestones are slated for the end of each month from November through April. That leads one tapster to project a May launch.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Does your organization use an IT service catalog?
Provide clear visibility of IT Services and capability of IT function
Need for ROI & VOI on investing in IT services (infratsructure & applications)
Interesting point of view. I disagree, it isn't needed. However think this makes clear how to do it. Aiming to not loosing respect, aligned with strategy. I'm sure other business areas have also clear lists of what they can and cannot do, and they don't loose any respect bc of that, only help the other business partners know what can you help them with. For example treasury can help me exchange usd and euros but choose not to allow other currencies if it's too cumbersome or expensive for them, and post the list of currencies they acept. I don't think it makes the entire Finance department any less strategic. I think the same happens with IT. Just becaus our servicedesk has a catalog stating we only install windows, not ubuntu, or MacOS we control costs and guide the business, doesnt mean the IT department or CIO any less C-level.
I appreciate sharing your insights but honestly, I don't agree with your observation. A value-based, business oriented IT strives to be recognized as a strategic partner to the business. This means that when it comes to IT budget, the real ROI must be measured from a business point of view. How much increase in business efficiency, sales, generated annual revenue, and improve in the company's competitiveness can be credited to IT to justify the IT expenditure. This is how progressive CIOs demonstrate their own value as a leader and the value their IT organization add to the overall success of the business. Provision of a service catalog is recommended by ITIL as a best practice in IT service management and if designed and implemented properly can reduce IT support costs and improve service delivery. If the IT customers don't believe IT is delivering value, it is because IT has failed to understand their business needs, strategic direction, operational challenges and has no metrics in place to prove its value. So having service levels that are mutually agreed do make sense. Having a clear definition of IT roles and responsibilities verses those of IT customers do make sense. Having an IT governance structure and process that promotes inclusion of the business in IT investment management do make sense.
I agree with your opinion up to a point. I think having a service catalog helps IT quantify what is of value. Value cannot be calculated without understanding the services IT provides in a structured way.

I agree with the article in that the establishment of a "charge back" model and/or "service level agreements" pushes IT towards being no more than a Telco or Electric provider. That and IT will constantly have to operate within the confines of that agreement, which doesn't foster partnering with the business.
Service catalogue should encompass enterprise wide service assets to deliver true value to business
The author talks about "partnerships" as being the primary focus, but if IT can not deliver on the services, then IT's credibility is destroyed, and won't be a partner for very long in the bigger picture. Unfortunately, for those of us who have been around 30+ years, we do see the trade-offs and a "service catalog" allows an IT organization to build credibility within the company and the various depts. once this credibility is established, partnerships are not far-off . . . And IT can discuss what other services, needs, plans, etc., the various depts have, and how they can work to deliver to that dept/company in a successful fashion. So, don't scrap the "service catalog" but work to deliver real SLA's with your customer base to prove the capabilities of IT not only for short-term, but long-term efforts, as well.
The danger of not having a catalog service ensures that IT can do any kind of service in any matter, which contributes to some form of anarchy and of course result in cost to the organization