The best approach for estimating user stories is one that- It allows us to change our minds whenever we have new information about a story Works for both epics and smaller user stories Doesn’t take a lot of time Provides useful information about our progress and the work remaining Is tolerant of imprecision in the estimates It can be used to plan releases It's no surprise that this one pops up often in Agile Scrum interview questions.