Agile Estimation Techniques

Estimation is hard. Even the most experienced development teams miss the mark with traditional time-based estimates. The most popular alternative, Planning Poker®, sounds fun, though it falls short in practice.

Relative estimation works for two reasons: 1) Our brains are naturally good at estimating the size of things relative to each other, and 2) We can learn from experience to make better decisions about the future.

This game allows a team to quickly review 5-15 items, organize them in relative rank order, and then assign a value scale to those items. Relative estimation is completed by comparing an item to the items around it to find where it falls in the prioritized list.

Agile release planning requires more than picking dates on a calendar. In this how-to guide, my colleague Kevin Rosengren provides a comprehensive review of the process and helpful frameworks to get the job done.