Like many organizations, we have been trying to understand how project management and (service) change management interact. There are a few confusing components:

• Project management texts sometimes use the term "change management" when referring to "project scope change management" aka controlling the scope of a project.
• Projects need governance. Change management also facilitates governance decisions.
• Very early on, it can be hard to determine if something is a project or not.
• Projects have products or deliverables, and these deliverables often follow a change management process.

Predecessors/Before You Begin

COBIT does not compete with ITIL or other bodies of knowledge. Separate bodies can be combined; in fact, ISACA has a mapping document that maps ITIL v3 to COBIT 4.1.

I received a notice from ISACA (the "Information Systems Audit and Control Association"), the people responsible for COBIT, that they are creating a new certificate called CGEIT--Certified in the Governance of Enterprise IT. You can outright get a certificate for the next couple of months if you have eight years of IT governance experience. After that, they'll start giving the exam in December.

Several bodies of knowledge include information about how to select vendors for providing services:

• PMBOK v3 chapter 12, "Project Procurement Management"
• COBIT AI3.1 "Technological Infrastructure Acquisition Plan," AI5.1 "Procurement Control," and DS2 "Manage Third-party Services"
• ITIL v3 Supplier Management

However, the most thorough body of knowledge we've found so far is Carnegie Mellon's "IT Services Qualification Center." They have created "eSCM-CL," a capability model for client organizations interested in "eSourcing."

Our training team has posted some of the department's training materials on the IS Training Materials website:

• ITIL Foundations Lite Training Presentation (pdf)
• COBIT Training Material (pdf)