Estimates are a contentious topic in software development, often causing friction between Product Owners (POs) and developers. POs rely on estimates to prioritize tasks in a backlog, balancing market demands with developer capacity. When faced with a mix of large and small features, POs must decide which to prioritize, especially if deadlines are looming. If a significant feature isn't completed on time, the release could fall flat, leading to dissatisfaction among users and potential financial losses. Estimates help POs gauge the feasibility of including high-value features within tight timelines. However, developers often find estimating frustrating. The challenge lies in the unpredictability of software development. POs expect estimates to account for unforeseen issues that may arise, but by nature, these issues are hard to predict. Developers appreciate the deterministic nature of code but face a chaotic reality when working on complex projects. As they dive into tasks, they frequently encounter unexpected complications, such as tightly coupled code that requires extensive refactoring. This uncertainty makes it difficult for developers to provide accurate timeframes, leading to frustration and a perception that estimates are an unrealistic expectation. The tension between POs and developers stems from differing priorities. POs focus on market needs and meeting deadlines, while developers aim for quality and minimizing technical debt. Technical debt accumulates when developers are pressured to deliver quickly, often at the expense of long-term maintainability. This creates a cycle where developers are forced to choose between quick fixes and a more robust solution, further complicating their ability to provide reliable estimates. Without understanding the implications of technical debt, POs may inadvertently set up their teams for future challenges. Ultimately, clearer communication and collaboration are essential for aligning expectations and improving the estimating process.