It's been nearly a year since Version 3 of the IT Infrastructure Library (ITIL) came out. The update to ITIL, a framework for best practices in IT service delivery, was intended to sharpen its focus and, not incidentally, to attract a new group of followers.

So did it? Well, yes and no. Early adopters have mostly high praise for ITIL Version 3. It is broader, deeper and better organized, and users say its "life-cycle" approach to IT service delivery is a major improvement over Version 2's more narrow focus on day-to-day operations and its disjointed collection of point prescriptions.

Still, not all users of Version 2 have rushed to adopt Version 3, which its authors call a "refresh."

Many say they are happy with the older version of ITIL because they have patched its shortcomings with other methodologies and homegrown remedies. And, they say, a comprehensive adoption of any version of ITIL is a huge task, often requiring a major cultural change inside IT.

ITIL was created in the late 1980s by an agency of the British government, now called the Office of Government Commerce (OGC), as a way to describe a systematic approach to the provisioning and management of IT services. ITIL became popular in Europe during the 1990s but didn't catch on in the U.S. until well after 2000.

ITIL was, and remains, literally a library of books, though the OGC also offers a raft of ITIL-related materials on its Web site.

Published in 2001, Version 2 focused on two pillars of IT infrastructure and operations: service support and service delivery. It prescribed best practices for incident, change, capacity and configuration management. Using those best practices, companies found that they were able to improve and standardize their data center operations.

However, important topics like security, financial management, the relationship between IT services and business value, and links between ITIL and other process disciplines got only lip service, if that, in the v2 ITIL.

And Version 2 tended to say what to do without specifying exactly how to reach that goal. Many companies liked that approach, saying it gave them freedom to adapt ITIL to their unique situations, while others complained that it left too much to the imagination.

In 2000, Microsoft Corp. put some of the "how to" into the Microsoft Operations Framework, its extension and enhancement of ITIL tailored to Microsoft IT environments.

For more enterprise computing news, visit Computerworld. Story copyright Computerworld, Inc.