Estimating is Easy – Or Is It? ​

Estimating is often seen as a straightforward and easy task, but in reality, it's a complex and challenging process. This is especially true when dealing with features that have never been done before or when using new technology. In these cases, it can be difficult to estimate the time required accurately. Additionally, the lack of experience and knowledge with these new features or technologies can lead to inaccurate or unrealistic estimates.

Poor estimating can be a significant source of tension between development and product teams. If the product team sets unrealistic deadlines based on inaccurate estimates, it can put undue pressure on the development team and lead to rushed and low-quality work. On the other hand, if the development team underestimates the time required for a feature, it can lead to missed deadlines and unfulfilled promises to customers.

To overcome these challenges, it's essential to identify the features with the most unknowns or risk and build proof of concepts. This approach involves developing a small and focused prototype that demonstrates the feasibility of the feature or technology. This prototype can help teams gain a better understanding of the problem and determine a more accurate estimate.

Another approach that can help with estimating is to break the work down into smaller, more manageable pieces. This technique, known as "chunking," allows teams to tackle the unknowns in smaller and more digestible parts. By breaking down the work, teams can identify the specific parts that are the most challenging, and allocate more time and resources to those areas.

In conclusion, while estimating may seem easy at first glance, it's a complex and challenging process. Estimating features that have never been done before or using new technology requires a more deliberate and structured approach. By identifying the features with the most unknowns or risk and building proof of concepts, teams can gain a better understanding of the problem and determine a more accurate estimate. Additionally, breaking the work down into smaller, more manageable pieces can help teams tackle the unknowns more efficiently. By improving the accuracy of estimates, development and product teams can work together more effectively, reducing tension and delivering better quality software.