Calculating the timing and cost of projects: how is this done and can the process be simplified?
If you've ever worked on developing custom applications, you are probably familiar with the fairly routine process of calculating the cost and timing of the project. And it would be nice if the calculation of the project was carried out only once, but often potential customers can not keep within the budget, and begin to change the requirements for the product on the move:
- It's too expensive, what if we do without the function X?
- * we do the calculation * So many.
- It's still expensive, but how much will it cost to develop only for the Y platform?
- * doing the recalculation * So many.
- Wow, that is, if we abandon the Y platform, we can do not only X, but also Z?
- * the next recalculation * Unfortunately no.
- It's a pity, then let's do without Z, how much will it cost us?
Standard ways of simplifying calculations, such as setting a fixed cost for a day of work of an employee or a company, usually lead to a loss of accuracy of results and still do not save us from manual calculations.
But, like any other process characterized by the words "routine", "accuracy" and "calculations," such calculations are likely to be automated. Let's see if this is really so.
Enter , you are welcome.