"Capacity management" seems to be overlooked in ITIL implementations--capacity management gets pushed way down the implementation plan, or is seen mainly as an input to event management (for alerts about disk filling up) and service level management (for making promises to users about what capacity will be available).

In Computerworld Magazine, Paul Ingevaldson recently wrote an article called "Top 10 qualities of a great IT shop." These qualities include the CIO reporting to the CEO, an executive steering committee, and a focus on the software development lifecycle.

A couple of the qualities relate to ITIL, such as having a security team (loosely Security Management), a disaster recovery process (IT Service Continuity Management), SDLC focus (very loosely Service Design), and participating in the long-range planning (Service Strategy).

The list looks OK to me, so I'm wondering: why don't ITIL concepts show up more often in Paul's list? Here are my guesses: