I personally like ROI better for comparing individual project, as the ratio lets you combine multiple projects for better return. Given the scenario of N projects of which you don't have funding for all of them, however, I think NPV of sets of projects--each of which maxes out the funding available (each of which has a positive NPV)--is the best comparison. I wouldn't try all possible combinations; I'd start with the ones that have the highest ROI and come up with several possible groupings that uses up the available funding, then pick the one with the highest NPV.
This assumes, of course, that each project is risk-free. That is rarely the case. As part of this exercise I'd try to make some reasonable guesses about how risky each project is. Is this something the team has done before (not very risky)? Is it new to the team (pretty risky)? Is it new to the world (very risky)? What's the likelyhood that a competitor will emerge that drops your sales--do you have strong barriers to entry (such as patents, regulations, customer relationships, or proprietary technology or distribution channel that's hard to duplicate), or is this an area that a strong competitor would naturally want to enter? What's the likelyhood that there is a supplier gets too much control and sucks up all the profit (think Intel and Microsoft for PCs). Discounting ROI & NPV for risk is not an easy task--there is no simple formula you can use. But to not include this as part of the analysis neglects what happens in the real world!
I also personally like the idea of doing some portfolio-style analysis on projects--some portion are low risk with low return, and some portion are higher risk with higher return. If the high-return projects pay off, that's great. If not, you've still got the low-risk projects to keep you going.
Exactly!! I tried doing MBA part-time while doing job but found finance a boring subject. Mathematical problems finance were interesting to solve but I found accounting horribly confusing...the balance sheet...oh!! I had to give-up for other reasons, but I was happy that I got rid of that...after all I like to spend time with electronics during that extra time became available...
But I agree that to be a good engineering manager or an entrepreneur, once should have good understanding of finance.
I actually though it would be a good idea to get an MBA part time.
When I finsihed my engineering degree, since I finished so far back in the pack, I decided that I wouldn't be a good engineer. I then did an MBA. It seemed to me an engineer as a manager was a good plan since a) you could get further organizationally and b) there were always managers who needed to understand what the engineers were doing.
Circumstances conspired and got me into engineering rather than management, and I have only recently moved part-time into management.
I actually thought it would be a good idea to get an MBA part time. My best classes were economics and the worst were accounting and business law. Coming from an engineering background, I found the whole cencept of law illogical.
A Book For All Reasons Bernard Cole1 Comment Robert Oshana's recent book "Software Engineering for Embedded Systems (Newnes/Elsevier)," written and edited with Mark Kraeling, is a 'book for all reasons.' At almost 1,200 pages, it ...