A majority of Agile teams use story points and planning poker for relative sizing and estimation purposes. If you ask a cross-section of people if estimation is necessary, the majority will reply in the affirmative. However, if you ask if they are able to do it successfully, you will find very few people who say yes.

One of the basic reasons is - software estimation in itself is a complex decision-making context. Any long-term estimation in the software domain is bound to be wrong. With an elongated span of time, the uncertainty increases and so does the variability in the estimation.

On the Product Backlog Item level estimation, though story points are used, most teams have their own interpretation of the subject. Eventually, story points in themselves have become a complex concept similar to pointers in the C programming language that most teams use it but rarely get it right.

A lot of material has already been written about Agile estimation. However, it becomes difficult to join all the dots together at one place for anyone to digest. This book is an attempt to simplify learning and make the concept as clear as possible so that people can simply say, "I get it".

This book is an essential guide for Scrum Masters, Product Owners, developers, and Agile coaches who want to refine their estimation techniques and ensure their teams can deliver value predictably and efficiently. Whether you’re new to Agile or looking to deepen your understanding, “Agile Estimation Distilled” provides the tools and knowledge needed to master the art of estimation in a world where uncertainty is the norm.