A Plan for Change
PMs are trained from day one of the importance of planning projects properly--the time invested in the planning stage is saved many times over during execution--so why don’t we do it with changes?
Broadly speaking project teams have two reactions to the change management processes that exist in a project--they are either the teeth that are used to frighten off anyone who wants to change the scope, timelines, etc., or they are the tool used to get what you want added to the project.
Good project managers know that change management has a vital role to play in ensuring that the project delivers the business benefit that was originally perceived, but how many actually know how to go about doing that?
Consider a project to produce an upgraded version of your company’s software product. During the code development, your major competitor announces that their next version is going to have a major feature that you don’t have--you must respond or face losing customers, big time! So what do you do? Initiate a project change, right? Well, maybe...
Let’s assume that you can’t ignore the competitor’s new feature, you still have options:
Add the feature and keep the same date by adding resources
Add the feature and slip the date to keep the same resources
Add the feature and keep the same date by removing other features
Please log in or sign up below to read the rest of the article.