I'm looking for some advice here - we have a number of different PM's in our organisation who have differing opinions on moving milestones on a roadmap.
Opinion 1) If an item is passed and is delayed (no matter why/when), the milestone will be moved to the current month/date
Opinion 2) If an item is passed and is delayed (no matter why/when), keep milestone where it is to show true delivery risk and time passed
Opinion 3) If an item is passed and is delayed (no matter why/when), drag it out past the current date to show the remaining work required.
What is the general best practice so we can all align?
Thank you Saving Changes...
Never do 1. It hides the slide. I can't see the rationale for using the current date unless you plan to finish today.
If you do 2, it looks like you have no plan to close the milestone, just that it's late.
If you do 3, it hides the slide. It just shows the milestone is in the future.
We often do a combination of 2 and 3 together. We keep the old milestone (red for past due) and add a new milestone (blue for new), with a line connecting them.
If too many milestones change, that makes schedules hard to read, so you need to re-baseline the schedule. Once you have struck a new baseline, use the new dates only for the milestones. Saving Changes...
After working with the project team to understand both the cause and impact of the delay, develop a plan and review it with your sponsor. Capture the cause and effect in your lessons learned, create a new baseline in your schedule, and adjust your plan/schedule to your new reality.
If you don't adjust your plan to your new reality, how do you estimate changes to the project completion date?
If a change request is submitted that affects the schedule, do you leave the schedule the same, ignoring the new work? Whether it's a change request or a delay, if you don't adjust your schedule you have the potential to create artificial deadlines that you will continue to miss. Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Dear Anonymous
Interesting your question
Thanks for sharing
Here you have a handful and valuable of opinions on the topic Saving Changes...
Anonymous
Thanks everyone, looks like we have a consistent reply and I'll take the learnings back to our PM team to work on this going forward. Saving Changes...
Nandkishor KhidkikarProject Manager Engr/Technical Manager Currently Seeking New Opportunities| CSSGB & Applied Project Management at University of California Irvine GPA 4.0Norwalk, Ca, United States
in addition to all above comments:
-Register (MOC) management of change for each approved change in scope of the project with notes on its effect of project cost, project schedule and project quality. Saving Changes...
Community Champion
