Resource Library

Nasser El-Batal will walk you through the most useful, recognized, and mandated ITSM best practices in the industry: TOGAF, COBIT and ITIL®. He will highlight the benefits of integrating them into a single implementation program to avoid project disaster. Discussions are focused on "Getting Your House in Order" and how to establish your own organization-specific business transformation program, while increasing your organization maturity.

The Open Group Architectural Framework (TOGAF) provides a structure for describing all transformational work within an enterprise. While TOGAF focuses on the role of an enterprise's architects, it also very much addresses the space in which business analysts (BAs) play. This can lead to role confusion, blurred deliverables, and duplicate work. In this one-hour webinar, business analysis expert and Global Knowledge instructor Adam McClellan will focus on those parts of TOGAF in which the business analyst is typically the most active, and he will outline how the analyst's work contributes to the broader architecture. He will also provide perspective for architects who work with BAs and for BAs interested in the architecture disciplines.

Traditionally, ITIL and TOGAF professionals have been part of different teams within an organization. Due to the ongoing alignment of business and IT, these professionals now often find themselves on the same team. Because of this crossover, there is a growing trend towards organization of work based on multiple best practice models. 

“Twisted Pair” is another way to identify a network cabling solution that’s also called Unshielded Twisted Pair (UTP) and was invented by Alexander Graham Bell in 1881. Indoor business telephone applications use them in 25-pair bundles. In homes, they were down to four wires, but in networking we use them in 8-wire cables. By twisting the pairs at different rates (twists per foot), cable manufacturers can reduce the electromagnetic pulses coming from the cable while improving the cable’s ability to reject common electronic noise from the environment.

I attended a meeting this week with a customer of mine and a potential new vendor. The new vendor was there to pitch his configuration and setup service offerings for a specific ITSM toolset. My customer has already had one bad experience with an ITSM tool configuration vendor who promised one thing and delivered much less. He ended up with a tool that’s minimally used and not configured to match his business needs. He’s looking for a vendor that can understand his business needs and priorities and quickly help him get his tool configured and working in a short time frame. Then the topic of standard changes came up. My customer asked for examples of standard changes. The vendor responded, “Server reboots are an example of standard changes.”