Good, experienced Agile software development teams know how to estimate well. But what happens if you’ve got a new team that’s never worked together before? Or what if you need reliable organizational metrics across a portfolio of Agile projects? How about if you need a structured, defendable way to estimate the budget for the whole project before development even starts? This discussion will feature an approach to estimating Agile projects that enables repeatability and consistency without sacrificing the flexibility and focus of more typical Agile estimation techniques. After all, what are stories if not functionality described from the user perspective?