The numbers. They are the hardest part of total cost of ownership. You will need time to get them clearer and clearer. You start out with some wild guesses, and you will refine them over and over again as more information comes available. And in the end, you end up with an estimation. An informed prediction.
Just keep in mind why you need the numbers. They are used for decision making with software selection. For this particular purpose it's ok to use a prediction. Actually, it's all you will have. It beats deciding based upon nothing.
This section will tell you all about the process of filling in the blanks; getting the numbers.
Â
3.1 Don't be afraid
You will have to provide numbers with a high level of uncertainty, you will not know exactly everything; but still, you have to tell the story, as early as possible.
This may seem a little unnatural for you, if you are used to be more or less sure before speaking to your managers. Consider the following section taken from “The Microwave Way to Software Project Managementâ€, the software project management guide I host on this site:
| Â "Son, what do you want to do when you grow up?"
A 'normal' child would just say: "Fireman, dad." Dad will smile, open a trust fund to put his son through college in the future, and will not slap him when on the kids' 20th birthday finishes his first year in medical school. That's a familiar situation! Now Dad talks to his boss… Should be familiar also. Dad is a professional Software Project Manager, he knows Planning (capital intended) and has learned by experience that if he can't keep the promise, he will not provide one. Funny though, that the two 'familiar' scenario's involve the same man. Why it is funny? Even though he knows that the changes his son becoming an actual fireman will be slim, Dad is satisfied with the answer and saves money based upon whatever assumptions he has. He has no idea if his son will go to college, if so, when, and he has no clue what it will actually cost at that time. But still, he reserves money for the future of his son. What might be Dads problem with 'it', which happens to be an information system? The answer provided to his boss is honest and probably the truth. However, his boss is not waiting for such an answer, he must have some statements to be able to run his business. So, even though his statements are true (let's assume), is it fair to claim that you have no idea? Fair to whom? To himself… well, he made his point; he told the exact view he has in his mind. But is it fair to just consider his own well being? Should he provide some statements to his Boss although he is highly unsure? Actually, the overall well being of the company is also in Dad his interest; if it goes bankrupt, he has no job (and his son will have no college fund). To keep the business healthy, the Boss has to have some vision on the future… How long will my people be involved in this project (so, out of their day-to-day operations). How much money do I have to reserve for this endeavor (you know, income and expenses should be inline with each other to run a business)? So, in his own interest he should provide some statements, just like his son. Consider why his Boss needs the claims for the future. First of all to anticipate expenses and extra resources, but also, to determine the overall course. All related activities within the company should be in tune with the strategy of this project. It's like crossing the ocean, you don't have to know the exact path you will sail, but just knowing that you aim to hit the coast at the opposite side, will help you plan a welcome committee at the other end. Some kind of vision will help the Boss steer the complete business in a direction, which will benefit Dad, his project, and the stability of his job, so in the end will help raising his son. Â |










Leave a Reply