Monday, July 16, 2012

Dear PM Advisor July 16, 2012

Dear PM Advisor,

Managing projects typically requires dealing with some level of change to what was initially planned and this is usually handled with a change management process. I have trouble handling items that come up as meeting action items or other small increments of change during the project that don't seem to warrant a change request. Do you always add these to the project schedule or do you keep them separate in an action list?

Signed,

Delta PM

Dear Delta PM,

There is definitely a whole continuum of changes expected on any project. Since no-one can exactly predict the future, change is expected. So what do you do with these changes as they become apparent. As with anything else, this depends. Let's look at what it depends upon:

  1. We find a better way to do work that costs less money, takes less time or increases scope without affecting any of the other constraints. Great! Just do it and report the good results in the next status report.
  2. Tasks are not affected in duration, cost or scope, we simply determined a different way to do it or discovered a few more sub-tasks required. Your Gantt chart should be at the task, not the sub-task level so don't add anything here. The task owner can adjust their sub-task list which may be in their head or written down.
  3. Tasks are negatively affected by the change but the critical path and the project budget are not affected. You need to report this but add that the overall project constraints are not affected. As a Project Manager you have the authority to take steps to manage these changes within the constraints given you by the Project Sponsor. They gave you enough time and money to complete the given scope. So manage this within the team and report to the Project Steering Committee. Note how this is different to the next situation. Do make changes to your Gantt chart.
  4. Changes cause the Project Scope, Quality, Schedule or Cost to change negatively. This is where you have exceeded your authority. Hopefully you have a Change Management Process in place that you can use to deal with changes of this type. You need to get the team together and work the change through the change control system. Determine the options the management team can take and the effect each option has on the Cost, Schedule, Quality, Risk and Scope of the project. Determine the team's recommendation for change. Recommend that to the Steering Committee. The Steering Committee may or may not agree with your recommendation. That is their right. Your job is to stick to the authority given you. Change your Gantt chart to reflect the change the Steering Committee came up with. Click on this link to see what happened to the hero of my book when he forgot this basic point.
So the bottom line is this. If the change does not negatively affect any of the project constraints, don't fill out a change request. You are managing within your bounds of authority. But report everything in your status reports, the more significant the change, the higher it should appear in your status report. Change your Gantt chart only at the task level, not the sub-task.

PM Advisor

Send me your questions at bfieggen@gmail.com

 

No comments:

Post a Comment