Estimates are a fundamental element of Scrum. Because they are the basis for planning and predicting when work will be completed. Like Sprints, if you’re not using Sprints and estimating, then you’re not using the Scrum framework.
In this article I'll begin discussing some lessons learned through pain and triumph in the real world, and try to boil them down to some Do’s and Don’ts with some real world situations.
Everything below the top level work item needs a parent for the backlog structure to work correctly. So as you create new work items, everyone should keep an eye on that. ScrumMasters should facilitate their teams backlog work and monitor their Backlogs for data quality problems like these.