Many people thinks that accurate project estimation is Rocket science. This makes some intuitive sense at first glance, it seems that estimation is a highly subjective process. But subjective estimations never help in any organization in any way :). Usually one person might take a day to do a task that might only require a few hours of another’s time.. As a result, when several people are asked to estimate how long it might take to perform a task, they will often give widely differing answers. But when the work is actually performed, it takes a real amount of time; any estimate that did not come close to that actual time is inaccurate.
Elements for successful estimation:
Good estimations can be achieved form good design. Good design can leads a good prediction and judgments, hence more realistic estimations. Good engineering estimates are possible only if you have two things: good information/design and good engineers. If the specs are crap, and a programmers are asked to come up with estimations it will be more scribbling ad hoc timings rather a good realistic, accurate timings.
A sound and realistic estimations can be achieved when we do work break down structure. Again work break down structure is something which can be achieved in different ways and it’s handy when you use previous project lessons learned and failures in estimations. Generally the more inspiring the final goal and challenging the deadline, the more key stakeholders are tempted to compromise on best principles of planning, management, control and also badly on quality as well :( which I hate always.
No comments:
Post a Comment