If you ask people what they like best about agile software development, nobody would say, "Sprint planning! I love having a hour long discussion over whether a story is a 3 or a 5!"

Sometimes, these difficulties come down to misunderstandings around relative sizing that can be easily corrected. However, there are ways of planning upcoming work and timelines that don't rely on any sort of sizing debates at all - relative or otherwise.

We'll take a look at a different way of measuring and projecting out work increments and timelines. If you are responsible for providing estimates and timeline expectations but have struggled with using story points or relative sizing to get there, these methods may work for you.

You'll learn:
- How to do planning around relative sizing correctly (if you're going to do it, do it well)
- What to measure to get actual data that doesn't rely on guessing
- How to use that data for planning, and how it can easily be misused
- Situations where one paradigm might work better than the other