ITIL is the IT Infrastructure Library, and just like XP, OS390, UNIX and a herd of other acronyms most people either don't know that or have forgotten, because like most acronyms it doesn't matter: it is just ITIL.
How it applies to your work depends very much on what your work is. We can broadly divide IT (IT = computing in business, not people mmucking around with computers) into two halves: development/solutions/applications and production/delivery/operations - call them what you will. If you work in that second half then ITIL has everything to do with you. It is the de facto standard for how to run an IT operation. It has been adopted by many large organisations. it is appearing in medium and smaller ones now. It is already appearing in job advertisments. It already forms the standard language for IT people to discuss operations: new staff, external cosnultants and auditors can understand how you do things by understanding how you vary from the ITIL model. It has formed the basis for a large chunk of the new ISO20000 standard. Either ITIl or ISO20000 will be a mandatory requirement for many IT outsource and other service contracts in coming years, and a mandatory qualification for employment in IT operations. All Service Desk tools are already expected to be ITIL compliant (whatever that means, hence this thread).
ITIL is a grass-roots movement: most management above CIO still haven't heard of it.
ITIL differs from TQM, Six Sigma and ISO 9000 in several ways: it tells you how to do stuff not what level to achieve, it is specific to IT process, and it is generally useful.
So if you are in ops you NEED to be across this thing.
The best introductory discussion of ITIL is on Wikipedia.