What is Diff b/w Cost Benefit Analysis & Marginal Analysis?
Both seems to be similar terms
--
----------------------------------
用加法計算我們的積累
用減法計算我們的消費
用乘法計算我們的投資
用除法計算我們的資源
來自深圳地鐵的溫馨題示
Harvinder: Cost-Benefit/Benefit-Cost Ratio that you have mentioned here is actually a technique used in Project Selection... not in Quality Planning where we determine whether it is worth doing a project by way of comparing cost vs. the benefits of the project. While Cost-Benefit Analysis is actually done in Quality Planning. Both your examples I feel belong to Cost-Benefit Analysis.
Before I start, let me tell you guys that PMBOK doesn't even talk about Marginal Analysis in Quality Planning, Rita Mulcahy does. PMBOK mentions only Cost-Benefit Analysis.
In fact Cost-Benefit Analysis and Marginal Analysis in terms of Quality Planning are inseparable just like Milk and water... Cost-Benefit Analysis (Milk) includes Marginal Analysis (water) :-)
Margin Analysis is the name given to the technique used in Cost-Benefit analysis.
In Cost-Benefit analysis, your aim is to determine whether or not to take a Quality Improvement Measure by comparing its cost with the benfit gained out of it. For Ex. a Quality Measure is to add Additional Test cycles in a project. You have to decide whether to add additional test cycles or not. To determine this, you would comapre the cost associated with adding one additional test cycle with its benefits. To make things clearer-- Cost associated with adding a test cycle is the cost of additional effort put for it and benefit of adding one test cycle is avoiding re-work worth certain amount of dollars.
Now suppose you determine that adding a new test cycle costs $100 and benefit gained is equal to value of avoiding rework worth $120.. hence you determine that adding one additional test cycle is benefitial by saving you $120-$100 = $20
Now just because adding one test cycle is benefitial, it doesn't mean that you go upon adding multiple test cycles and still save money by avoiding re-work. This is exactly where Marginal Analysis comes into picture... Marginal Analysis is the name given to the technique of determining how many more test cycles can be added before it starts hurting (meaning the point where the cost of adding further test cycles overshoot the benefit gained).
For Ex. After adding the 1st test cycle (example given above by me), you have saved $20 because cost was $100 but benefit was $120... now you have to determine whether you should add 2nd test cycle or not.. 2nd test cycle should also cost somewhat similar to 1st one i.e. $100 but benefit will not be same.. because using 1st test cycle you would have avoided re-work for 40 defects but now using the 2nd test cycle you might be avoiding the rework for only 35 defects .. hence money saved in 2nd cycle will be $105 (simple maths.. 40 defects cost $120 hence 35 defctes cost $105)... hence you determine that even adding 2nd test cycle is benefitial because cost is $100 and money saved in terms of re-work is $105 (benefit of $5)...
Now you have to decide whether to add 3rd test cycle or not... again you detremine that adding a 3rd test cycle would cost you $100 but it might be saving you from the re-work of only 30 defects... so the money saved here for 30 defects is $90 (simple maths.. because 40 defefcts cost $120 so 30 defects would cost $90)... Now here we see that adding a 3rd test cycle is not benefitial because it costs $100 but saves re-work worth only $90.
Hence, our Cost-Benefit analysis has shown that adding more test cycles is benefitial and at the same time Marginal-Analysis tells where to stop adding more and more test cycles... i.e. don't add after the 2nd test cycle..
Dear Harvinder,
I do lots of ANALYSIS on the personal/professional front to make lot many decisions and I call that analysis as Cost-Benefit ANALYSIS and Marginal ANALYSIS :-)
But here in this forum my responses/examples are based upon PMBOK's definition of the terms. As you know PMP exam is very particular about definitions given in PMBOK... no deviation is permitted :-)
Your examples were fantastic... no doubt about it... And we are actually subjected to such situations while managing projects.
But to appreciate the benefits of the milk you need to drink the milk :-) I suggest you read through the entire mail of mine for it to make sense.
Regards,
Brijesh Tripathi, PMP