Tomorrows leaders...

 Tweet from TweetCaster 



Location : Address not available
Posted via Blogaway

What is IT Architecture?

Having been a carpenter for 20+ years, I have to go back to that model. You have a group or board set building codes that are specific for your community. You have architects that take those building codes, the site plan, and customer needs and design a structure. That structure starts with artist renderings various options before it gets to the detail level. Once the customer selects the option they like, the Architect is committed to provided detailed plans and all the accompanying schedules (documentation). These plans may need to be reviewed or approved by a logical building or zoning board. It is only when these have been complete that the General Contractor can provide a cost and time estimate. At this point, the contractors are accountable to build the building to the architects specifications (which are aligned with the building code). The contractors work is incrementally inspected by building inspectors to ensure that the building meets or exceeds the building code.
So who has accountability?
The architect maintains accountability to design to the building code. If the building is constructed to the plans, the architect maintains accountability. If the contractor "improvises" or diverges from the plans, accountability shifts to the contractor. This is also true if there is a structural failure in the building.

How does this translate to IT Service Management?

Seven Myths of SAAS Debunked

As with any disruptive new technology that threatens the business of established older technologies, negative talk about software as a service has elicited plenty of FUD (fear, uncertainty, doubt) during sales presentations and negotiation sessions. Service-now.com CEO Fred Luddy and marketing director Matt French, who run a SAAS provider, offer their responses to that FUD.

• Myth No. 1: SaaS is not secure. [FALSE]
• Myth No. 2: Using SAAS is a risk to compliance. [FALSE]
• Myth: No. 3: Over a three-year period, SAAS licensing is more costly than typical client/server application licensing.[FAlSE]
• Myth No. 4: SAAS is suited only for small and medium-sized businesses. [FALSE]
• Myth No. 5: SAAS is only offered in a hosted model. [FALSE]
• Myth No. 6: SAAS applications are not customizable. [FALSE]
• Myth No. 7: Nobody is adopting SAAS. [FALSE]

Excerpts from an article written by Chris Preimesberger (2008-10-28)
http://www.eweek.com/c/a/Cloud-Computing/Seven-Myths-of-SAAS-Debunked/

Do I really need the IT Infrastructure Library (ITIL)?

I found some of these statements from the IT Skeptic and added some others... Do you disagree?

• You don't need ITIL to run a static environment where nothing goes wrong and nothing changes and nothing grows.
• ITIL has nothing to do with technology, nor can it be implemented with just technology.
  
• ITIL is about how an organization and the people within it respond to planned and unexpected variations in the environment, from outages to changes to growth.
• ITIL seeks to make the IT organization more responsive to the business needs and to help demonstrate value
• ITIL defines human behavior.
• Every organization needs the processes ITIL describes.
• Every organization already has them.
• ITIL is just one way of defining a standard approach to performing them.
• You may not need ITIL but every IT shop needs to be doing what ITIL describes, one way or another.