How to Crash a Project in Project Management using the Critical Path Method (CPM)
ฝัง
- เผยแพร่เมื่อ 11 ก.ย. 2023
- How to Crash a Project in Project Management using the Critical Path Method (CPM). We will cover what projects are suitable for crashing, the steps for crashing the project, and the activity crashing formula. We will conclude by walking through the Milwaukee Paper Project Crashing example that is taken from the textbook and solve the crash costs. We will crash the project by 3 weeks (going 1 week at a time, so 3 total activity crashes). This content is derived from the Textbook "Operations Management, Sustainability and Supply Chain" 13th edition by Jay Heizer, Barry Render and Chuck Munson. Chapter 3 on Project Management.
You can get free copies of this slide deck and other chapter outlines on our website at www.operationsuniversity.org
Outstanding job teaching how to crash a project!
Thanks Kare, I appreciate the feedback!
Hey I am currently going through your playlists on this channel, I must say: I am very happy and gratefull that you provide such great, high quality and engaging videos. Your video's and expertise are truly appreciated
Hi Louis, thank you for the nice feedback. I appreciate the kind words. I am glad you find the videos helpful, that’s the whole reason that I’ve decided to post them!!! Thanks again.
Good Work on Crashing
Thanks for the feedback!
if when we find the critical pathway and then they tell us the crashing potential for each varaible. do we reduce each variable by the crashing potential??
I am just confused on wether we reduce only one variable (i.e. the cheapest one.) or if we reduce each varaible from the critical path
Hi Sara, with project crashing you will pick the cheapest option (activity) that is on the critical path. You will crash it once. You do not crash every variable on the critical path. In my examples that will take your projects down by 1 week. If that gets you to your desired result, then you are done. If you need to expedite the project more, then you would crash the next activity that is the lowest cost option again, and it must always be on the critical path. You keep doing this until you get the project down to the desired duration. Does that answer your question?
@@OperationsAndSupplyChain yes thank you so so much!
At 17:00 When the critical paths are A-C-E-G-H and B-D-G-H, why isn't there an option to crash activities E and D for a Total of $2,000 just like Option 1 of crashing activities C and D?
Hi Jad, I had to think about this one! Technically you are correct, there is also the option to crash activities E & D just like C & D. Activity C has a crash cost of $1,000, which when combined with D @ $1,000 adds up to $2,000 (but that is still more than G @ $1,500). Activity G is the correct activity to Crash because it has the lowest Crash Cost. Good question, thank you.
@@OperationsAndSupplyChainPerfect! Thank you for the reply
How do you know the critical path if you not given
Hi Grace, if the critical path is not given you will have to solve for it. That is Step #3 of the CPM Method. After you calculate the slack of every single node/activity in the project, only then will you be able to determine the critical path (which is the longest duration through the project).
how do you know when you should stop crashing? like how low do we go
Hi Sara, the question will tell you when to stop crashing. For example, if the project has a total duration of 17 weeks, but it needs to be completed in 15 weeks, then you know that you will need to crash the project by 2 weeks.
@@OperationsAndSupplyChain Makes sense thank you!! I was wondering what if they dont tell you when it needs to be completed like if I get a chart and I see that there is two paths for example
a-b-f (23 days)
c-d-e-f (20 days)
Would I basically take the critical path a-b-f and try to get it down to 20 days? then afterwards I look at the two paths and see if I can decrease it by one or two days without exceeds the limits of my cost?
Thank you again for all your help and time!!
In my humble opinion that would be a bad question. It would need to ask specifically how much they wanted the project crashed otherwise you would just crash the maximum amount possible and waste money.