“How to we associate T-shirt sizes of epics to get a date?”

“How many of these features can we get done in H2?”

These are common questions that cause lots of pain in product development. Commonly people turn to labor intensive approaches such as planning poker of massive epics which are no more reliable than a guess.

What if we could answer those questions reliably without having to estimate every story or even break them all down from the epics.

Come learn how to use reference class estimation to work out the overall size of large scale efforts before you do a single story breakdown.

You must be a Member to view this post and you are currently not logged in.

You can either log in below or sign up here.