Change Management

Member Content= Member Content

Knowledge Shelf articles are available at no cost to all PMI members. Join today to take advantage of this and many other member benefits.

A Change Management System Based on Pareto’s Law Member Content
- by Al DeLucia, PMP, Director GSA PMO (retired), GSA Mid-Atlantic Region
The author’s team conducted a business process review to analyze a large database of changes. The benefits from the resulting change management system outlined in this article, including reduced change order processing times, better definitions of team member roles, and empowerment of the people closest to the action, contributed to improved project quality.

Managing Changes Using Standard Practices Member Content
- by Omar Ali Beg, PMP
Project management practitioners will face many change management challenges. The main purpose of this article is to provide standard guidelines, including change request templates, to project, program, and portfolio managers on how to implement an integrated change control system in their organization.

Key Elements of a Change Request Member Content
- by Linda K. Miller, PMP
What is the minimum amount of information that an effective change request should include and why is it needed? What do established change management systems usually require? This article looks at the change management process defined by the Information Technology Infrastructure Library (ITIL), a methodology used in many service management groups in IT organizations.

Ten Change Management Tips for Information Technology Project Managers Member Content
- by David Norman, PMP
The goal of this article is to offer practical strategies that will help you manage change effectively. The background and examples in this document have an IT bias, because the author took many ideas and examples from recent experiences managing change for 2 years in a $US20 million dollar database migration project. This project had it all-extended duration, large number of critical business intelligence applications in scope, two external vendors, and several other "critical" projects taking place in the same time frame. Change had to be managed or change would have devoured the project.