Day: 17 March 2006

I remember reading a while ago, a discussion about making the decision to build a complex peice of code now which contains more functionality than is required, compared to building a simple version now and having to pay more in the future to add that extra functionality (cost in future is higher because of inflation, having to remember what your code is about, paying for the time where the business is on hold waiting for the new functionality, etc). I sadly can't remember where I read it, but it didn't give too much info so I wasn't able to do such a calculation on my own. Then yesterday I was in a meeting where we discussed about how the version of eGate we are using is only supported on Windows 2000, and MS is about to stop supporting that. So should we move to the next version of eGate and to Windows 2003, or should we stay as we are and take the risk that if a bug occurs on Windows 2000, that we won't be supported by MS... Well, I got out my book called "The 10 Day MBA" which I bought a few years back and started to look into the problem. It turns out that there are several tools, namely "Decision Theory (DT)", "Net Present Value (NPV)" and "Expected Monetary Value (EMV)"... The solution goes like this: 1) Draw a tree diagram with all the decisions on it. In this example, we have the following (sorry for…

Read more