Enhancing Project Estimates with the "Risk Driven" Approach
I have made numerous wrong estimations in my life. The common mistake was being too optimistic about implementation. I was thinking only about successful user paths that could be easily followed, without considering what could go wrong. There were also other errors like being afraid to give too big a number, or not asking the client enough questions to truly understand the scope of work. Of course, now we have an agile working style, where we are planning new sprints constantly, but if someone starting a new business needs to build a mobile app, website, and backend, then it’s important for them to know the budget.