In our last post, we have clarified the gist of the Business Analysis Process. While Business Analysis is strictly reserved for project development, estimation is something we, as people, all contribute to in our everyday lives. Coming up with the shortest route to work, calculating the expenses of holidays, or even planning out our meals all leave us with something we estimated.
Today, we have interviewed Piotr Tomaszewski, WORKITNOW’s CTO and our project estimation expert. We have broadened our knowledge about the importance of such a process. What exactly is needed to prepare the high-quality estimation? How does it affect the client and the crew? How to master it? Is it that important? Find out about Piotr’s answers down below!
Project estimation is “the process of analyzing available data to predict the time, cost and resources needed to complete a project”. It is a vital part of the software development process. “In IT, (when it comes to the fixed price model) estimates at the time of signing a contract transform into commitment” says Piotr. Project estimations include scope, time-frames, budget, and risks.
“In order to estimate anything, it is crucial to get data on which to base the estimates” – states Piotr – “the less information we have, the less accurate the estimation is. The more data we have, the higher the level of accuracy is”.
Usually, clients turn to estimators with some sort of concept or idea that they want their product to base on. Piotr says that those are the most difficult estimates:
“We can translate the concept into our idea of how it will look like. We have our vision, and we can put it together from our perspective”.
The more client gives from their point of view, the better they have developed and specified their idea, the more precise the initial valuation is. The project estimator divides the concept into smaller pieces that are easier to analyze.
Project estimation changes whether clients choose a fixed-price model or a time-and-material model. Fixed-price projects clients get their project estimation sup front. It is possible to price only particular fragments, but it all comes down to one thing. In order to change the part of the project, it is essential to price everything again from scratch. “Fixed-price projects are artificially agile. You can divide them into sprints and show the stages of work to the developers, but that’s not the point. A fixed-price project does not allow you to make a turn. It does not go hand in hand with real agile” says Piotr. In time-and-material projects the valuation is calculated for time spent. It is possible to turn around and change a decision. To find out more about the differences between these two cooperation models, check out our “Fixed Price or Time &Material?” article!
Piotr Tomaszewski has a lot of tips to share with both clients and project estimators.
“Good practice for the valuation of projects that are very general, not detailed and there is not much information is to submit a range (e.g., “this will take 20/30hours because it can go either way”). It is important in the estimation to precise which units are used (whether we’re talking about days, hours, or sprints)”. Piotr mentions the fun way in which developers can communicate the“size” of the given project between each other: “I have even seen cards with fruit. The pineapple is going to hurt and if it is a raspberry then good because it is small”.
The final estimations based on the analysis should be prepared by people who will be programming the product.
“Ultimately, the developer should have a say, because they will develop the product. On the basis of the analysis, that is, as we go through the process of clarifying the concept of the product with the client, where the result is usually documented in various types of documentation(stories, analysis), we get such comfort that we can refine the estimate. The developer can estimate the project independently so that there is no impact from the initial estimation. Then we collide these valuations and analyze them”.
It is not that easy to estimate a project. A lot is at stake – one of the most important factors is the experience of the estimating employee. It can take hours of research and contemplating to get satisfactory results especially when the client is not sure about what exactly they want to achieve.
“We have a number of patterns resulting from the experience, that give us the ability to predict how much something is going to cost and how much time is needed to complete it” adds Piotr.
Project estimators learn from previous estimations.Projects repeat and most systems are similar.
“When we present the initial estimation based on our assumptions, we welcome our clients to discuss it further. It is not crucial to immediately decide whether the client is eager to go forward. We leave a proposal to perform an analysis. Initial estimation is a stage of our work – the customer engages and forms a relationship with us”.
Project estimation is a crucial part of project development. Without even one of the aforementioned contents, the development process becomes longer and flimsy, which results in wasting time and money.
In this field of work, it is especially valued to have experience and a good understanding of the client’s area and the problem.
“Minimization of risk, avoiding estimating alone, the confrontation of the valuations are crucial parts to construct the estimation of a high standard” says Piotr Tomaszewski. “Estimation is still a kind of a lottery. You need a lot of practice to result in a win-win situation”.
Were you aware of the importance of the project estimation? Let us know your thoughts.
Oops! Something went wrong while submitting the form