There is a statement: to be successful in projects estimation it's necessary to have a solid background and experience. Because it's our experience that says "it will take 2 weeks to deliver that feature" and it's our experience that can specify confidence level or probability of such estimate being hit. Our brain accumulates knowledge and experience taken from one successful or failed project to another in order to further provide an expert view on how much time something similar could take again in the future.
One of the ideas, that stands behind the Estimatess.io is that if estimates are based on the empirical approach, it's possible to create, accumulate and re-use company knowledge that serves as the basis for projects estimation.
For that purpose, Estimatess.io has two components, that together build the knowledge base: the technical knowledge and the evaluation of the resources involved.
To build a technical knowledge base, Estimatess.io suggests going to the "Technologies" page, create there the ones company works with and fill them in with the pre-defined average estimates. For example:
Such technical knowledgebase can be maintained, expanded and updated regularly, making the estimates more and more accurate with every estimated project.
Another knowledge base component comes from the evaluation of people, who work with companies. It's and often saying: "We'll be working with experts, who need just half of the average time to deliver such project". Another often phrase: "He's junior, give him more time for this job, he needs twice more than you think". These statements show that speed of work, knowledge, the experience of developers (any many more worker-related factors) have a good impact on the time we foresee for the web projects. Simply saying, there's a human factor there. So Estimatess.io suggests having this human factor recorded so that estimates could be adjusted accordingly. For that, there's a parameter in the developer's profile: performance coefficient.
Now, how those two will be used?
Once estimation is requested - you create a project and go to estimate builder to review and evaluate uploaded files. When breaking down your big project scope to smaller working pieces you will be able to use what's already in your knowledge base.
The performance coefficient will be used on the analytics page. When playing around and checking who could be the best assignee for the project, the performance coefficient will be used to
1. adjust the original estimate and show the time that will be required for the selected developer(s);
2. show respective costs for comparison with the original budget.
That way, when analyzing projects, it's possible to use the technical knowledge and the evaluation of the resources involved to be more accurate and reliable in web projects estimates.
Try out the Estimatess.io tool and make your estimation process smarter!