In Agile, prioritization is essential, and there are a lot of different prioritization frameworks out there - a subject I’ve delved into previously (
Agile Prioritization Mastery: Learn the Top 4 Techniques!). Many prioritization frameworks fundamentally lean on a couple of pivotal criteria: the value delivered to the customer or business, and the effort or work required to complete tasks.
Consider this: You have two items on your to-do list, both offering identical value to the customer. However, one task, let’s call it item A, is considerably more substantial, requiring triple the effort compared to the other, item B. Which one would you tackle first?
The practice of estimation nudges you towards starting with item B, the smaller task. Why? Because it allows for quicker delivery, ushering immediate value to the customer and enabling you to gather feedback sooner. This initial feedback could be instrumental, potentially influencing and improving the approach towards completing item A. On the contrary, diving into the larger task first leaves the customer waiting longer for value, while also delaying the reception of valuable feedback. It simplifies the prioritization process, ensuring that value is delivered swiftly and improvements are continuously integrated.