Ramesh ChalamalasettiPMI ATP Instructor – PMP®| PMI Certified Instructor - PMP Exam Prep®Hyderabad, Andhra Pradesh, India
We learned (might be experienced as well) that we may come across "Multiple Critical Paths" in our PM journey from cradle to grave. Well, what's the best way to bid adieu to multiple CPs? Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
In large projects, there are always multiple CP's but I did not get your question. Can you ellaborate more please ? Thanks.
...
1 reply by Ramesh Chalamalasetti
Feb 01, 2016 3:17 AM
Ramesh Chalamalasetti
...
@ Rami: Thanks for the query. Yes, project volume impacts plurality of CPs. Can we minimize this plurality to a single longest CP such that we can attack it productively? As Ahmed suggested, reshuffling dependencies is one way. Like wise, I wish to learn vital few ways or one best way. Hope I'm clear now. Thanks.
Saving Changes...
Ahmed KararProject Engineer| Ministry of Water Resources, Irrigation and Electricity Khatoum, Khatoum/ Jabl Awlia, Sudan
As I understand that, How can we avoid the Multiple Critical Paths???. So let me first say that why we try to avoid them to take place. simply, more critical paths is high level of risk. Now to answer the main question, you can avoid them by rethink of dependencies. As we know there four type of dependencies among them is a discretionary one which is also known as Sot logic or preferable dependency. thus, you can look into dependencies and try to break the discretionary ones and joint them with other activities to see what will happen. then there is to possible things might take place, the first one is that the risk has reduced by decreasing the number of critical paths or you will find out new critical paths as to last movement. So it is not easy to do unless you use an excellent schedule tool.
I hope that help. Saving Changes...
MAEN QADDOURAHProject Director| AJ SAUDIJeddah, Saudi Arabia
in large projects.it is common Saving Changes...
PANKAJ KUMAR JOSHIGeneral Manager| Transrail Lighting LimitedNainital, Uttrakhand, India
In large projects multiple critical path are normal and cannot be avoided..
If we try to avoid it through change of dependencies the risk may reduce but the project duration will increase.
Sometime when we recheck schedule, we find that many activities can be done in parallel which are unnecessary creating another path. You can revise your schedule for such activities.
...
1 reply by Ramesh Chalamalasetti
Feb 01, 2016 3:40 AM
Ramesh Chalamalasetti
...
Thank You Pankaj your view is pretty valid. We might mitigate/eliminate the risk of multiple CPs by reshuffling dependencies but there's a possibility for escalated duration impacting base lines, perhaps. Well, is that not a risk especially when we have stringent deadlines? In my view, we're compromising on something for something else - right? Instead, can't we sit with key stakeholders for their buy-in denovo? Just trying hard to have bench mark solution my friend:)
Saving Changes...
Ramesh ChalamalasettiPMI ATP Instructor – PMP®| PMI Certified Instructor - PMP Exam Prep®Hyderabad, Andhra Pradesh, India
@ Ahmed: Your views resonate with that of mine partially/majorly. Thank You. Yes, reshuffling dependencies more on discretionary dependencies that mostly occupy soft corner is one of the ways to address multiple CPs. I wish to learn the root cause or vital few causes of this kind of critical care health level of our projects. Can we afford to look at this from defective planning, poor BR analysis, or some thing wrong in prioritization so on.. Saving Changes...
Ramesh ChalamalasettiPMI ATP Instructor – PMP®| PMI Certified Instructor - PMP Exam Prep®Hyderabad, Andhra Pradesh, India
Feb 01, 2016 12:42 AM
Replying to Rami Kaibni
...
In large projects, there are always multiple CP's but I did not get your question. Can you ellaborate more please ? Thanks.
@ Rami: Thanks for the query. Yes, project volume impacts plurality of CPs. Can we minimize this plurality to a single longest CP such that we can attack it productively? As Ahmed suggested, reshuffling dependencies is one way. Like wise, I wish to learn vital few ways or one best way. Hope I'm clear now. Thanks.
...
1 reply by Rami Kaibni
Feb 02, 2016 2:22 AM
Rami Kaibni
...
Now got your point Ramesh - I guess the gentlemen's feedback was good enough. It is always better to try to reshuffle and check the dependencies (If they were discretionary) and end up with one CP and take the risk into consideration. Two CP's are bearable but more than that, the risk will be very high.
Saving Changes...
Ramesh ChalamalasettiPMI ATP Instructor – PMP®| PMI Certified Instructor - PMP Exam Prep®Hyderabad, Andhra Pradesh, India
Feb 01, 2016 3:05 AM
Replying to PANKAJ KUMAR JOSHI
...
In large projects multiple critical path are normal and cannot be avoided..
If we try to avoid it through change of dependencies the risk may reduce but the project duration will increase.
Sometime when we recheck schedule, we find that many activities can be done in parallel which are unnecessary creating another path. You can revise your schedule for such activities.
Thank You Pankaj your view is pretty valid. We might mitigate/eliminate the risk of multiple CPs by reshuffling dependencies but there's a possibility for escalated duration impacting base lines, perhaps. Well, is that not a risk especially when we have stringent deadlines? In my view, we're compromising on something for something else - right? Instead, can't we sit with key stakeholders for their buy-in denovo? Just trying hard to have bench mark solution my friend:)
...
1 reply by PANKAJ KUMAR JOSHI
Feb 01, 2016 2:42 PM
PANKAJ KUMAR JOSHI
...
I agree, we must involve stakeholders for such discussions. We must minimize critical paths for proper control and to avoid any risk in project. Use what if scenario or modeling technique to analyse all options.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
As other mentioned it could be normal mainly in large projects. But as other mentioned you have to work with your schedule to have only one at the end. The way to do that have been mentioned above. Any action you will take will create a risk unless the orginal schedule was not right and becuase the action you have optimized it. Saving Changes...
PANKAJ KUMAR JOSHIGeneral Manager| Transrail Lighting LimitedNainital, Uttrakhand, India
Feb 01, 2016 3:40 AM
Replying to Ramesh Chalamalasetti
...
Thank You Pankaj your view is pretty valid. We might mitigate/eliminate the risk of multiple CPs by reshuffling dependencies but there's a possibility for escalated duration impacting base lines, perhaps. Well, is that not a risk especially when we have stringent deadlines? In my view, we're compromising on something for something else - right? Instead, can't we sit with key stakeholders for their buy-in denovo? Just trying hard to have bench mark solution my friend:)
I agree, we must involve stakeholders for such discussions. We must minimize critical paths for proper control and to avoid any risk in project. Use what if scenario or modeling technique to analyse all options. Saving Changes...
Ashok PatraProject Manager| Tech Mahindra LtdBhubaneswar, Odisha, India
I agree to most of the points mentioned above. Managing dependencies both resource and schedule will help us to eliminate critical paths. In important cases when we need the decision or consent from critical stakeholders we should involve them. But every time we should evaluate project risks. Saving Changes...
Community Champion
