![]() | Advertise on this site |
| | |||||||
| Home | Project Management Forum | Software and Book Reviews | Project Management News | Register | Mark Forums Read |
| | LinkBack | Thread Tools | Display Modes |
|
#1
| ||||
| ||||
| Hi All, First time posting my thread here, I am working as a planning engineer in a high rise residential project, we've got a baseline program and used to submit montky proress report to the consultant every month... Mostly what's happening with internal finishes activities is that these are not happening as per the retained logic given in the program...and hene mostly the successor happens first and the predecessor happens later and hence i used to schedule using the constraint- progress over ride rather that retained logic- but the consultant is adamant and insists the retained logic should be followed .... And I am forced to go for it and each time takes the existing link out to get the schedule prpoerly... To what extend you find this consultant sensible, when we are trying to substantiate the changed logic is basically intended for acclerating the works on site.... Kindly put across your insights on this, Francis ![]() |
|
#2
| ||||
| ||||
| Hi Francis, welcome to the forum! IMO, the schedule should be a roadmap for the project execution. If you are not executing the work according to the schedule, then the schedule needs to be revised to reflect the new reality or it is pretty meaningless as a measuring stick or management tool IMO. Of course, disagreements over changing the schedule between the owner and the executor can be more of a financial concern than a project management concern and that sometimes can be detrimental to the end result in and of itself.
__________________ "I love it when a plan comes together." - Colonel John "Hannibal" Smith, A-Team Do you have experience using project management software? Write a review! |
|
#3
| ||||
| ||||
I agree As PM schedules are composed in advance, sometimes tasks might be logically be completed a little differently than envisioned, with task "B" taking precedence over "A". Still, these anomolies should be few and far between. Deviations from the project plan and schedule should not happen consistently and maybe the resolution for this issue is to communicate to the overall PM. |
|
#4
| |||
| |||
| I tend to agree with PMKB on this issue. I could not have said it better. |
|
#5
| |||
| |||
| The fellows here are right... your schedule need not to be a perfect one but as workable as possible... else you might not be able to justify any claim that you could have in the future... goodluck..!! |
|
#6
| ||||
| ||||
| as one Project Director once said, "We make people move, not the COMMITMENT." ![]()
__________________ pepkoRn |
| Thread Tools | |
| Display Modes | |
|
|
| | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Practice Standard for Scheduling | pmkb | Scheduling | 3 | 08-24-2006 05:47 AM |
| Dissertation papers on planning and scheduling | pmkb | Planning | 4 | 08-24-2006 05:45 AM |
| scheduling algorithms | barthelemy | Scheduling | 2 | 01-25-2006 06:52 AM |