We recently got a copy of IT Governance: How Top Performers Manage IT Decision Rights for Superior Results.  It's written by Peter Weill and Jeanne W. Ross, and was published in 2004 by the Harvard Business School Press.

I like seeing how each source defines IT governance.  This book's definition is

Specifying the decision rights and accountability framework to encourage desirable behavior in IT.

 
I have been doing some research into "IT Governance," trying to understand which of our available resources are authoritative on the subject.  The main sources I've found are EDUCAUSE ECAR (research) articles, Gartner articles on "IT Governance," and last but not least ISACA's Governance section.

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.