Main Menu
Home / IT Governance / 5 Reasons for Making Change Management a Top Project Priority

5 Reasons for Making Change Management a Top Project Priority

Nobody gets into programming because they enjoy the tension of waiting for errors to emerge during compile. Likewise, nobody gets into project management because they love a good change request. Still, change management is a critical aspect of project management, and it warrants your attention. In a post for the Association for Project Management, Brad Egeland highlights five reasons to make it a top priority:

  1. Eliminate gold plating
  2. Increase revenue
  3. Increase project profitability
  4. Keep the project on time
  5. Keep the project on budget

Lead the Change

“Gold plating” can sound like a good thing if you do not know what it is, but it refers to developing a needed feature/product beyond what the project requires. It is work that does not yield sufficient business value, and thus is time (and money) not well used. In the worst case, it even introduces new unanticipated risks. Change and scope management allow you to identify and halt gold plating, saving project resources.

The abilities to increase revenue and project profitability go hand in hand:

By paying very close attention to scope on the project the project manager and team will … be able to keep profitability as high as possible on the project. Making sure that all work performed is either part of the original work required (and thus costed out and being paid for by the customer) or part of a new change order and … being paid for by the customer is critical. No change order in place just adds cost with no associated revenue[,] resulting in decreased profitability. Tight change management means no free work is being performed by the delivery team[,] and that means no added costs that have no revenue associated with those costs – keeping profitability at or above … planned levels. Your CFO will be happy.

More obviously, making changes to the scope of the project allows it to stay on schedule and within budget in the face of newly arising needs. Or at the very least, formal changes can allow a project to stay on track according to an approved revised timeline and budget. It is only when managers shun change requests and adopt an attitude toward risks of, “Eh, we’ll work through it” that the project really falls into danger.

You can view the original post here:

About John Friscia

John Friscia is the Editor of Computer Aid's Accelerating IT Success. He began working for Computer Aid, Inc. in 2013 and continues to provide graphic design support for AITS. He graduated summa cum laude from Shippensburg University with a B.A. in English.

Check Also

7 Habits of Highly Effective Release Managers

Release management is a big deal, in that it is usually the thing underscoring statements …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time